Project

General

Profile

Actions

Task #3430

closed

Can't login to the TDF wiki

Added by Eyal Rozenberg over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Normal
Category:
Single Sign-On
Target version:
-
Start date:
Due date:
% Done:

0%

Tags:

Description

I once had an account on the DF wiki. I tried logging into it recently and failed. So, I tried recreating it.

That supposedly succeeded - I got a confirmation email, clicked it, and supposedly my details got saved - but when I now try to login through the "Login" link at the top of the wiki page, I am directed to here:

https://wiki.documentfoundation.org/index.php?title=Special:UserLogin&returnto=Main+Page

and the page says:

Log in

User cannot be authenticated.
[ ] Keep me logged in

and there's a button saying "Login with Pluggable Auth". The button does nothing, apparently.

Actions #1

Updated by Eyal Rozenberg over 4 years ago

I wrote the hostmaster, and answered. Guilhem says:

We migrated to our Single Sign-On service about 2.5 years ago, see
https://listarchives.tdf.io/i/-PHZkfZmlW5fzZ3MldOUDJ9o

Your account wasn't automatically linked because your old wiki account
1/ has the same username, and 2/ has a different email address. Are you
still able to receive messages to @technion.ac.il (without the ‘alumni’)
label prefix? If so, please add it as secondary address in your SSO
profile at https://user.documentfoundation.org/edit . This should allow
the linking script to kick in.

Well, first, this information doesn't excuse the page I was redirected to. I should have gotten a page explaining why I can't be authenticated, and suggesting relevant courses of action.

Also, I am not able to receive email at my old address, so I couldn't follow Guilhem's advice.

Actions #2

Updated by Guilhem Moulin over 4 years ago

Closing this, will follow up on the hostmaster thread.

I should have gotten a page explaining why I can't be authenticated, and suggesting relevant courses of action.

There are various reasons why authentication fails and no one-size-fits-all solution. Also the authentication backend change happened 2.5 years ago after 6 months showing a banner and sending out regular announcements, so in practice very few active users are affected. These days admins are very seldom poked about this indeed.

Actions #3

Updated by Guilhem Moulin over 4 years ago

  • Status changed from New to Closed
Actions

Also available in: Atom PDF