You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by "ichait-bgl (via GitHub)" <gi...@apache.org> on 2023/10/09 23:22:55 UTC

Re: [I] Reuse/Migrate users to use SSO [superset]

ichait-bgl commented on issue #21273:
URL: https://github.com/apache/superset/issues/21273#issuecomment-1754052965

   Not sure if this will help, but we had a similar setup. Started with vanilla user/pass auth and then enabled SSO via Jumpcloud.
   
   If a user was already created through user pass, when they logged in via SSO, a new user record would be created because the field values (e.g. username) used to created the user initially were different to those coming from Jumpcloud.
   
   What worked for us was to edit any existing user records so that the fields would match what would come from Jumpcloud. Then when the user logs in via SSO, Superset seemed to just match them with the existing user and all worked fine.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org