feat(providers): Add ssoready-saml
provider
#11314
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
☕️ Reasoning
This PR adds a provider,
ssoready-saml
, for SSOReady. SSOReady is a set of open-source dev tools for enterprise SSO: https://github.com/ssoready/ssoready (I work on it)The
ssoready-saml
provider works similarly to the existing BoxyHQ, Osso, and WorkOS providers. It integrates with an OIDC-compliant OAuth server that proxies for a SAML 2.0 flow; we use the JWKS+id_token
-based way of providing user data to the OAuth client. Because of the similarity, I based the code and docs in this PR based on those existing providers. Sorry in advance if I got the precedent wrong!The flow this provider integrates with is documented here: https://ssoready.com/docs/saml-over-oauth-saml-nextauth-integration
An example website using this provider is available at: https://ssoready-nextauth-demo.vercel.app/ (source code here). In the interest of proving this really works, that app will log you in, over SAML 2.0, to a real Okta instance that I've set up. The credentials you'll need to input into Okta are shown in the demo app itself.
🧢 Checklist
🎫 Affected issues
None I'm aware of.
📌 Resources