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
OpenID Connect #4205
Comments
I agree with this. Just to be clear, OpenID support doesn't necessarily mean using closed services like GitHub or Facebook as assumed in the old discussion at #795. One could also have their own internal setup using something like SimpleLogin or a custom auth backend (something that I, for one, would find very useful). |
Still hoping for this for use with my own OIDC server. |
Would be great to login users to Wallabag using OIDC. Then I don't need to login to every service I use. For Wallabag client apps, a seperate app password should help to be compatible with existing apps. |
any update on this? |
I'm really interested in this feature too ! |
Could this be prioritized. This is the only features that is holding me back from self-hosting wallabag |
@hibare unfortunately it is not considered as a priority for now, as we need to work on the symfony 5 update |
Too bad, look forward to this feature too. This is a good project, thank you for your work! |
Really need this, to use my own e.g. Nextcloud or KeyCloak as IDP. |
+1 for me, I would like to integrate it with Authentik! :-) |
It would be useful to be able to enable OpenID Connect SSO functionality. A basic OpenID Connect library is available here that works with self hosted OIDC Provider solutions such as KeyCloak. This could also enable so called social login with ie. guthub credentials.
This single sign on solution is useful for users that host several apps, and want to streamline and simplify user management and authentication across apps.
The text was updated successfully, but these errors were encountered: