SAML is Now in Public Beta
We're excited to announce that Clerk now supports SAML-based Enterprise Single Sign-On (SSO). As of now, the SAML feature is in public beta, with general availability expected later this summer. Clerk’s new SAML SSO feature was carefully built to improve the secure authentication experience for both you and your customers:
Integrate with Top Identity Providers
Clerk's new SAML-based Enterprise SSO feature allows you to seamlessly integrate with top identity providers such as Okta, Azure AD, and Google. The integration process is straightforward, and our docs provide an in-depth glossary for correctly mapping IdP claims to Clerk fields.
Secure, User-friendly Authentication Experience
When SAML is configured, your users enter their email address on your sign in page and, if the email matches an active SAML connection, they will be redirected to the configured IdP for a secure login using their credentials. Best of all, this seamless authentication experience works out of the box with Clerk's UI components.
Public Beta & Configuration
While in public beta, SAML is available at no cost for all customers subscribed to a Business plan. However, once SAML transitions to general availability, the pricing structure will change, with SAML being billed at $50 per connection per month.
To get started, go to your dashboard and navigate to User & Authentication > Enterprise Connections. From there, click on "Create Connection" to begin the setup process.
For detailed instructions on configuration and mapping IdP fields to Clerk, please see the docs.
Other Fixes & Improvements
- Thanks to community contributions, we now have localization support for additional languages:
- Satellite domains can now be removed using the Clerk Backend API.
- Multidomain support has been extended to Node/Express applications.
- Users will now be notified via email when modifications are made to their primary email address.
- We've extended user imports to include support for Django's bcrypt SHA256 password hasher.
- New contribution guide for open source contributors who want to open pull requests to our open source Javascript SDKs.
- For greater interoperability across various build tools and frameworks, we now facilitate both ESM and CJS builds in
@clerk/clerk-react.
- Added support to
@clerk/nextjs for Next.js apps deployed to AWS Amplify and Railway.
Resources
- How to Add Seamless, Full-Stack Authentication in Next.js: In this tutorial, Zevi Reinitz demonstrates how to incorporate authentication into your Next.js app using Clerk.
- How We Roll: Multifactor Authentication: In the 3rd chapter of "How We Roll," Colin Sidoti, Clerk's CEO, breaks down how we think about and build Multifactor Authentication (MFA) at Clerk.
- Send SMS Directly from the Browser: In this tutorial by Gabriel Manor, you'll discover how to transmit SMS messages directly from the browser using Frontend-Only Authorization (FoAz).
- How We Roll: Email Verification: In the 4th chapter of “How We Roll,” Dev Agrawal provides an in-depth look at how Clerk implements email verification during sign-up, sign-in, and account management, using strategies like one-time passcodes, verification links, and Single Sign-On (SSO).
- A big thank you to Petr Doležal, Ahmet Polat, Ilya Nikishin, and Cali Castle for your help adding additional localization support to Clerk.
- Shoutout to Pranav for the launch of Swiftube, a React app that uses Clerk (for authentication) and transforms user prompts into animated videos. Learn how it was built in this post.
- Kudos to the team at Tunnel, who just launched this week using Clerk, for making it easier for developers to tunnel their applications locally.
- Congratulations to the folks at Maple, who also launched with Clerk this week, for introducing a new platform for privacy-focused analytics.
Stay tuned for future updates. If you have feedback or suggestions, leave us feedback on the docs via Docsly, tweet us at @clerk, or join the Clerk Community on Discord.
