#10946 User reports of "Authentication token is no longer valid; new one required" errors from SSO when logging in
Closed: Upstream a year ago by kevin. Opened 2 years ago by mattdm.

See the reports here https://ask.fedoraproject.org/t/fedora-account-creation-issues-report/25447 from various users. Although they are trying to log in to Ask Fedora, the errors are coming from the Fedora SSO side, and it isn't necessarily Discourse-specific problem.

We do continue to get new signups, so it's not universal -- but seems like enough people are hitting the problem that we're getting numerous reports from people who persisted and got through -- as one person in that thread kind of crankily points out (but it is a good point), there are probably many more who give up at that point.

Help please. :)


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: authentication, high-trouble, medium-gain

2 years ago

I'm not sure what could be going on here.

It's almost like sometimes when a new user activates their account and sets their initial password it's somehow expiring that password right away?

I just made a test user and when I activated it and entered my initial password, I got an error:

 Your account has been created, but an error occurred while setting your password (<html> <head> <title>200 Success</title> </head> <body> <h1>Password change rejected</h1> <p> <strong>The old password or username is not correct.</strong> </p> </body> </html>). You may need to change it after logging in. 

and sure enough, checking the user in the admin ui I see:

Password expiration: 2022-10-27 22:42:19Z

@abompard any ideas here? I can refile upstream if you prefer, but this definitely looks like a noggin bug (or something broken in our infra around that) .

Metadata Update from @kevin:
- Issue close_status updated to: Upstream
- Issue status updated to: Closed (was: Open)

a year ago

Version 1.7.1 contains what I think is the fix for this issue. It has been released and deployed a couple minutes ago, so this shouldn't happen anymore.

Login to comment on this ticket.

Metadata