3
Generic SAML Login Provider
Source: outline/outline#2155 · opened by @routerino
I've noticed that you're doing work to make generic login providers a thing, and it's fantastic.
However, you're only opening up specific login providers at a time (starting with Microsoft). This seems to go against the idea of having a generic protocol for people to use.
It would make a lot more sense to provide a generic "third party provider" button that instead uses the [saml]( protocol, which passport [supports](
That way rather than having to create a specific use case for *every single provider*, you can just create one. A SAML template that other IdPs can integrate. Most major IdPs can integrate SAML in some form or another, and it vastly reduces the work you have to do to integrate on a per provider basis.
However, you're only opening up specific login providers at a time (starting with Microsoft). This seems to go against the idea of having a generic protocol for people to use.
It would make a lot more sense to provide a generic "third party provider" button that instead uses the [saml]( protocol, which passport [supports](
That way rather than having to create a specific use case for *every single provider*, you can just create one. A SAML template that other IdPs can integrate. Most major IdPs can integrate SAML in some form or another, and it vastly reduces the work you have to do to integrate on a per provider basis.
No pledges yet. Be the first to back this.
Comments
Similar requests
Config Option to forward login to /auth/oidc instead of the normal login screen.
3 votes · 0 comments
Enable PKCE for OIDC flows
2 votes · 0 comments
Support for Generic OpenID Connect Identity Providers
11 votes · 0 comments
Allow magic link login even if the email is enrolled with an SSO provider
3 votes · 0 comments
Ability to keep slack integration but remove 'log in with slack' from the login screen.
6 votes · 0 comments
No comments yet.