|
|
|
|
|
The Clerk team has been hard at work shipping new features to help you build secure applications faster. Here’s a rundown of the highlights:
|
Introducing Custom OAuth Providers
|
|
|
|
One of our most requested features is now available for all users: Custom OAuth Providers! Starting today, you can add any OpenID Connect (OIDC) compliant OAuth provider to your Clerk application.
|
-
Automatic configuration: Simply provide an OIDC Discovery Endpoint and we’ll take care of the rest.
|
-
Manual configuration: If the desired service does not have a Discovery Endpoint, you can configure the necessary values yourself.
|
|
|
|
|
iOS SDK Beta
|
|
|
|
We’re excited to announce the Clerk iOS SDK is in Beta! This SDK is a toolkit that enables developers to integrate Clerk into their native iOS, macOS, and other Apple-native apps using Swift.
|
-
Built with Swift in mind: Harness the declarative approach to user interface on all Apple platforms.
|
-
Async/Await support: Use the latest in Swift networking to make your code as readable and expressive as possible.
|
-
Social Connections and OAuth: Authenticate with your favorite social providers in just a few lines of code.
|
|
|
|
|
Other Features, Fixes & Improvements
|
-
Local Credentials in Expo: We’ve expanded our Expo SDK to support the concept of Local Authentication (ex: Face ID, Touch ID, etc).
|
|
|
Resources
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Community Highlight: Per User Database Starter by Turso
|
|
|
|
Our friends at Turso recently launched the Turso Per User Database Starter. It is an open-source boilerplate repository built with Next.js that uses Clerk to create isolated SQLite databases in Turso for each user who signs into the application.
|
|
Simply create a Turso database, configure a Clerk application, and launch it to Vercel!
|
|
|
|
|
|
|
|
|
