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

feat(providers): Add ssoready-saml provider #11314

Closed
wants to merge 2 commits into from

Conversation

ucarion
Copy link

@ucarion ucarion commented Jul 2, 2024

☕️ 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

  • Documentation
  • Tests
  • Ready to be merged

🎫 Affected issues

None I'm aware of.

📌 Resources

Copy link

vercel bot commented Jul 2, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
auth-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 18, 2024 8:22pm
1 Skipped Deployment
Name Status Preview Comments Updated (UTC)
next-auth-docs ⬜️ Ignored (Inspect) Visit Preview Jul 18, 2024 8:22pm

Copy link

vercel bot commented Jul 2, 2024

@ucarion is attempting to deploy a commit to the authjs Team on Vercel.

A member of the Team first needs to authorize it.

@github-actions github-actions bot added providers core Refers to `@auth/core` labels Jul 2, 2024
Comment on lines +133 to +135
client: {
token_endpoint_auth_method: "client_secret_post",
},
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can this be inferred from the .well-known/openid-configuration? If so, I can't seem to figure out how.

Copy link

stale bot commented Jan 21, 2025

It looks like this issue did not receive any activity for 60 days. It will be closed in 7 days if no further activity occurs. If you think your issue is still relevant, commenting will keep it open. Thanks!

@stale stale bot added the stale Did not receive any activity for 60 days label Jan 21, 2025
Copy link

stale bot commented Jan 31, 2025

To keep things tidy, we are closing this issue for now. If you think your issue is still relevant, leave a comment and we might reopen it. Thanks!

@stale stale bot closed this Jan 31, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
core Refers to `@auth/core` providers stale Did not receive any activity for 60 days
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant