Clerk as an OAuth Provider.

[mchennupati]

Goals

1. Currently NextAuth allows Auth0 as an OAuth2 provider, can we also add an plug and play for Clerk as well
2. One could then avoid having to specify the custom template.
3. Allows for easy switching between competing providers.

Non-Goals

1. Simple addition of provider, no additional features required.

Background

The current alternatives is to create your own configuration file in this form:
https://github.com/nextauthjs/next-auth/tree/v4/packages/next-auth/src/providers

The clerk oauth2 can be created using this:
https://api.clerk.com/v1/oauth_applications

And it is in this form:
{
"object":"oauth_application",
"id":"xxxxxx",
"instance_id":"ins_xxxx",
"name":"nextauth-clerk",
"client_id":"xxxxx",
"client_secret":"xxxxxx",
"public":false,
"scopes":"email profile",
"callback_url":"https://yourapp/api/auth",
"authorize_url":"https://clerk.yourapp.com/oauth/authorize",
"token_fetch_url":"https://clerk.yourapp.com/oauth/token",
"user_info_url":"https://clerk.yourapp.com/oauth/userinfo",
"created_at":1701767138671,
"updated_at":1701767138671
}

Proposal

Add a new clerk.ts file to providers here: https://github.com/nextauthjs/next-auth/tree/v4/packages/next-auth/src/providers

[MatteoGauthier]

Hey @mchennupati is the code you provided working?

[mchennupati]

Hey apologies for the delay, the short answer is I couldn't get around making it a custom package so I could import it. Cloning it, adding this line and getting a new npm package (the last bit was a but too much as I got entangled in type errors etc :))
So I ended up removing nextauth and just adding clerk.

[MatteoGauthier]

Thanks for your reply ! I choose to use Logto as a provider, an open source authentification service with a lot of enterprise features, it's a Auth0 alternative.
Cheers

[masoncfrancis]

@MatteoGauthier have you been able to use Logto with NextAuth? I’m exploring authentication options and I really like it, but I’m trying to figure out what it would take to implement