Skip to content
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

Hox about renaming Keycloak strategy to OIDC or OpenIDConnect #126

Open
pini-gh opened this issue Nov 15, 2020 · 4 comments
Open

Hox about renaming Keycloak strategy to OIDC or OpenIDConnect #126

pini-gh opened this issue Nov 15, 2020 · 4 comments

Comments

@pini-gh
Copy link

pini-gh commented Nov 15, 2020

The Keycloak strategy actually relates to OIDC which is not specific to Keycloak. I've used it successfully to authenticate with LemonLDAP::ng as OIDC provider.

Renaming it to OIDC or OpenIDConnect would advertise its capabilities better than its current name does.

@Hanspagh
Copy link
Contributor

Hi @pini-gh
I think that would be great
Would you have the time to change the Keycloak to a more general OIDC client?
I think it is mostly the naming that needs to be changed to avoid the confusion with Keycloak?

@pini-gh
Copy link
Author

pini-gh commented Dec 20, 2020

Hi,
Unfortunately I can't take care of that. I'm not a web developer and I don't know elixir at all. I just stumbled upon Ueberauth while configuring a Mobilizon [1] instance to authenticate via OIDC / LemonLDAP::ng.
[1] https://joinmobilizon.org/en/

@simonedavico
Copy link

But what would be the difference with ueberauth_oidc?

https://github.com/DefactoSoftware/ueberauth_oidc

@pini-gh
Copy link
Author

pini-gh commented Jan 31, 2023

But what would be the difference with ueberauth_oidc?

https://github.com/DefactoSoftware/ueberauth_oidc

I didn't now about this one. Then there are 2 different OIDC auth module for Ueberauth.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants