I have a problem very similar to Avatars not pulling from SSO . While users can login with my SSO provider ( consideratio/discourse-sso-oidc-bridge ), and discourse show up information in logs about it, the provided information about the signed in user being admin or not etc is ignored. In other words…

I had multiple issues, resolving them did the trick for me. My group names needed to meet certain cirteria: must be at least %{min} characters must be no more than %{max} characters must only include numbers, letters, dashes, and underscores must be unique must be present must begin with a lett…

Suspicion 1 Discourse manages to say “User was logged on” and list “admin: true”. Am I correct to assume that when this happens, the user is meant to become an admin if the user wasn’t already? Or, does it require additional steps? I saw the following from Setup DiscourseConnect - Official Single-S…

Suspicion 2 When I inspected the logs further, I found that params listed does not contain the full sso param, but only a truncated part. What is going on here? The only information within the sso params that is truncated is nonce=01bcdfd0a32b809567991b3dbd59fe9f&return_sso_url=https%3A%2F%2Fdiscour,…

Code inspection I tried to figure something out, but I failed… Starting point - Discourse gets user information from my SSO provider I found my way here by spotting the “User was logged on” text from /logs in Discourse. app/controllers/session_controller.rb fdf4145d4 …

[image] consideRatio: Discourse manages to say “User was logged on” and list “admin: true”. Am I correct to assume that when this happens, the user is meant to become an admin if the user wasn’t already? Yes, setting the SSO parameter admin to true should be all that’s required to log a user …

Ah thanks for confirming that @simon ! Yepp the issue persist and I have failed to find another clue on what may be wrong. =/

Is this for a forum that we are hosting, or is it a self-hosted site?

This forum is a self hosted site, using a SSO provider I’ve written myself based on previous work of others ( GitHub - consideRatio/discourse-sso-oidc-bridge: Discourse SSO OIDC Bridge - A Python PyPI package · GitHub ).

Enable verbose SSO logs, logout, log in with a user that sends the admin flag in the payload, check logs.

No, it doesn’t. Click on the entry, then on the tabs below, and it will have every key in the payload and the respective value in a table format.

SSO provider implementation - Admin, moderator and groups ignored?

Support

consideRatio (Erik Sundell) April 4, 2019, 8:10am 11

@falco thanks, it does only contain the kind of warning log entry about a sso request starting and another log entry indicating a successful login.

Topic		Replies	Views
SSO is forcibly creating the user as an admin Bug	12	1399	September 16, 2021
Can't make user admin, reverts when logging in Support	9	1735	May 30, 2019
I lost my admin rights due to misconfigured SSO SSO	7	818	May 7, 2020
Allow extra metadata from Single Sign On Feature	6	1392	July 22, 2014
SSO - "There is a problem with your account. Please contact the site's administrator." SSO	16	4966	March 18, 2019

SSO provider implementation - Admin, moderator and groups ignored?

Related topics