bonamim opened a new issue, #21273: URL: https://github.com/apache/superset/issues/21273
When we created the **Apache Superset** instance we kept the **default login form** (_user/pass_). However, we need to switch to using **Google SSO**. This change has already been configured in the development environment, but we have verified the following situation: - If the user already exists with the same email that the person is trying to access, the following error message is displayed ❌  - If the user doesn't exist, a new one is created and everything is normal ✅ **Environment** - browser type and version: Chrome (Version 104.0.5112.101) - superset version: superset version 2.0.0 - any feature flags active: - `ENABLE_TEMPLATE_PROCESSING` - The config inside the Pod: ``` config_oauth: | CSRF_ENABLED = True # This will make sure the redirect_uri is properly computed, even with SSL offloading ENABLE_PROXY_FIX = True from flask_appbuilder.security.manager import AUTH_OAUTH AUTH_TYPE = AUTH_OAUTH OAUTH_PROVIDERS = [ { "name": "google", "icon": "fa-google", "token_key": "access_token", "remote_app": { "client_id": os.getenv("GOOGLE_KEY"), "client_secret": os.getenv("GOOGLE_SECRET"), "api_base_url": "https://www.googleapis.com/oauth2/v2/";, "client_kwargs": {"scope": "email profile"}, "request_token_url": None, "access_token_url": "https://accounts.google.com/o/oauth2/token";, "authorize_url": "https://accounts.google.com/o/oauth2/auth";, "authorize_params": {"hd": os.getenv("AUTH_DOMAIN", "")} }, } ] # Map Authlib roles to superset roles AUTH_ROLE_ADMIN = 'Admin' AUTH_ROLE_PUBLIC = 'Public' # Will allow user self registration, allowing to create Flask users from Authorized User AUTH_USER_REGISTRATION = True # The default user self registration role AUTH_USER_REGISTRATION_ROLE = "Gamma" ``` **Question** - Is it possible to reuse or somehow migrate existing users? Because if it is not possible, we will lose all relations between the user and the object created by him/her. -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
