Apr 08, 2022
Apr 08, 2022
OAuth after Sign Up, mergeable custom metadata, improved observability, and optional usernames - plus, try our Clerk x RedwoodJS authentication integration!
OAuth connections can now be be added after a user has signed up.
This can be accomplish through the <UserProfile/> component, or through the useUser() hook and the user.createExternalAccount() function.
Metadata fields can now be updated via deep-merge in addition to complete replacement. This functionality was added to the Backend API to start.
We updated our Next.js and Node SDKs to add a `Auth-Result` header when the authentication state is unknown or signed out.
This will help us debug situations where your backend thinks the user is signed out, but the frontend knows they are signed in. Usually the reason for this is quite benign, but it can be tricky to debug.
Usernames can now be optional, instead of only Required or completely Off.
You can make the change from the "Email, Phone, Username" settings page in your dashboard:
We'd like to wish a hearty congratulations to RedwoodJS on their v1 launch.
We've had a shared Slack with the Redwood team for a few months now as we collaborated to build the Clerk integration. The folks there are incredibly kind, patient, and innovative and we can't wait to see how the framework evolves.
Learn more about our RedwoodJS authentication integration.
Start completely free for up to 5,000 monthly active users and up to 10 monthly active orgs. No credit card required.
Learn more about our transparent per-user costs to estimate how much your company could save by implementing Clerk.
The latest news and updates from Clerk, sent to your inbox.