SSO gives us an HTTP 419, but works

Support
1

What sorts of SSO messages should I be looking for in the discourse logs?

Our discourse redirects, which used to work previously:
'${process.env.DISCOURSE_URL}/session/sso?return_path=${encodeURIComponent(forumUrl)}'

have started yielding:

Login Error

Account login timed out, please try logging in again.

with an HTTP 419 coming back from ${DISCOURSE_URL}/session/sso_login, but the user is authenticated and able to click on the site logo and continue.

Where’s the best location in the discourse logs to track details reflected about this change we’ve introduced, and any suggestions moving forward (save reverting our changes)?

2

Try enabling the verbose discourse connect logging site setting. With that setting enabled, some extra log entries will be added to your site’s error logs page (found at Admin / Logs / Error Logs.)

2 Likes