-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failback in case of SSO failure #31
Comments
Just removing the oidc settings should work as far as I remember |
Well this is actually what I tried but I ended up landing on login screen without nor the SSO button nor the user and password fields... |
@bufferoverflow I just confirm the behaviour mentioned before, if settings are removed this is the outcome I've found other weird behaviours in the management of users created by the plugin, I don't know if you wish to have an issue opened for that also or if I should stop bothering. I'm quite sure you developed this plugin for your use case so I guess it's already perfect for your needs, I was just wondering if you would be willing to make some slight adjustments in order to make it even more adaptable to different environments. |
Sadly there is currently no way to have alternative login options. We would be really happy to review any MRs about it though. This is mostly based on the sentry-auth-google plugin from Sentry itself at the moment. |
Thanks, do you know how to disable it from CLI, as mentioned disabling the config lines in sentry.conf.py is not working |
you would need to uninstall the plugin. But this will not change the users. |
Hi everybody
I know this is not an issue related to the software itself, rather is something related to emergency cases
I noticed that once this plugin is configured and enabled there's no way (or at least I've not found any) to have a failback to login locally with the initial administrator configured.
Do you know how this can be achieved? There's any command that can be issued at machine/container level to disable OIDC SSO and have back the login form?
Thanks in advance
The text was updated successfully, but these errors were encountered: