Closed YassinEldeeb closed 2 years ago
I'm willing to contribute adding this, wdyt?
The plan is to start with LinkedIn
OAuth cause the product is mostly for business so LinkedIn is a great OAuth option to have.
we won't be adding more OAuth providers yet as some studies have shown it's better to have email + one primary SSO provider and Google is the biggest one so far.
it's really really hard to remove OAuth providers later
I'm not quite sure whether this is the right place to ask but therefore it is also not possible to authenticate against an selfhosted authentication provider (i.e. Authelia, Keycloak, Authentik, GitLab)?
Because I thought that the integration OpenID Connect (OIDC) or OAuth2 providers is similar everywhere and only URLs and secrets differ?
Most applications provide a possibility to add this via ENV variables for selfhosted solutions and a GUI like this when the ENV variables weren't provided. Projects like GitLab also support this via their settings file.
So there's no need for having provider specific logic (only maybe some defaults for URLs and secrets). Am I mistaken here? :thinking:
openId Connect is really needed and easy to implement
Hello, just checking if there has been any progress on this, we would love to be able to integrate with keycloak and OIDC protocol
Describe the solution you'd like
Adding one or two of the following OAuth providers as OAuth options to the login page.
Github
Twitter
LinkedIn