Jimmy-Newtron commented on issue #12939: URL: https://github.com/apache/superset/issues/12939#issuecomment-820685788
> I set up SSO login for Superset successfully by setting up the config file to use OAUTH2 login and integrating it with OKTA SSO service. However the redirect uri http://[site]:8088/oauth-authorized/okta that needs to be configured for Flask Application Builder to work redirects to a Superset sign-in page where the user needs to choose a provider and click sign-in. This is an unnecessary step since there is only one provider and the user already logged into OKTA SSO provider and should not need to sign-in or login again. > > Is there any way to bypass this redundant sign-in page which my users find confusing and sometimes get stuck on. If there is no way to bypass it can someone tell me how I can customize the login page to instruct users how to use it? In fact you have the possibility to override the login/logout endpoints by the creation of a custom View class that will replace the default sign in page You can have a look at the example in the discussion https://github.com/apache/superset/discussions/13915#discussioncomment-558709 The only difference is that you have to assign your class to `self.authoauthview` variable If I am not clear I can share more information about it -- 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. For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
