SSO Plugin Account login timed out, please try logging in again

(Dean Peterson) #1

I have a link that goes directly to tradeClient.

If it has been a while since visiting that link the user will get “Account login timed out, please try logging in again.” If I visit the exact link again, the user is successfully logged in and I do not receive the error message. My question is: if the account login is timed out, why doesn’t the discourse system go ahead and call my external sso url like it does the second time? It’s as if, first, the user has to attempt going to a url in discourse and get the error message. Discourse notices and saves some setting. The second time, discourse knows the user is logged out and correctly calls the sso flow. Why can’t it immediately call the sso flow and skip the “Account login timed out” error? In fact, it seems in previous versions of Discourse I did not have this problem.

(Felix Freiberger) #2

I don’t know – I suggested doing this here:

(Dean Peterson) #3

@fefrei You still have not found a solution?

(Felix Freiberger) #4

I’m not suffering from this – it was just a recommendation from me, hoping to be picked up by the Discourse team :slight_smile:

(Dean Peterson) #5

Oh, well that is good you’re not dealing with this. It is not a good user experience.


I am experiencing this same issue with my own SSO server running that’s providing authentication for other services, as well as Discourse.

Have you come across a solution for this for yourself?

(Dean Peterson) #7

I was running multiple containers taking SSO requests. I was retaining a bit of state between requests and if a single user jumped between containers, I lost the state I needed and received the error. Temporarily I scaled down to one container.

(Denis Heraud) #8

I would very much like this to be fixed as it’s pretty confusing for the average user (as they have to reload the browser page to log back in).