Azure AD Authentication with Next.js and Prisma #445
+176
−14
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Al that is needed are the following environment variables: AZURE_AD_CLIENT_ID= AZURE_AD_CLIENT_SECRET= AZURE_AD_TENANT_ID= ALLOW_DANGEROUS_EMAIL_LINKING=true (Somehow it doesnt work without this) OAUTH_EXCLUSIVE_LOGIN=true (Shows only Sign in with Azure AD button)
Oops.
sinamics
reviewed
Jun 21, 2024
| @@ -26,6 +26,7 @@ chmod +x /usr/local/bin/ztmkworld | |||
| # apply migrations to the database | |||
| echo "Applying migrations to the database..." | |||
| npx prisma migrate deploy | |||
| # npm install && npm run dev | |||
Comment on lines
+62
to
64
| "expires_in" INTEGER, | ||
| "ext_expires_in" INTEGER, | ||
| "token_type" TEXT, |
There was a problem hiding this comment.
are these really neccessary?
I can try without but seems necessary according to documentation next auth.
Comment on lines
+111
to
142
| // { | ||
| // id: 'azure-ad', | ||
| // name: 'Azure Active Directory', | ||
| // type: 'oauth', | ||
| // version: '2.0', | ||
| // authorization: { params: { scope: "openid profile user.Read email" } }, | ||
| // accessTokenUrl: 'https://login.microsoftonline.com/{tenantID}/oauth2/v2.0/token', | ||
| // authorizationUrl: 'https://login.microsoftonline.com/{tenantID}/oauth2/v2.0/authorize', | ||
| // clientId: process.env.AZURE_AD_CLIENT_ID, | ||
| // clientSecret: process.env.AZURE_AD_CLIENT_SECRET, | ||
| // }, | ||
| AzureADProvider({ | ||
| // id: "azure-ad", | ||
| // name: "Active Directory Azure AD ", | ||
| // checks: ["state", "pkce"], | ||
| // authorization: { params: { scope: "openid profile user.Read email" } }, | ||
| allowDangerousEmailAccountLinking: | ||
| Boolean(process.env.ALLOW_DANGEROUS_EMAIL_LINKING) || true, | ||
| clientId: process.env.AZURE_AD_CLIENT_ID, | ||
| clientSecret: process.env.AZURE_AD_CLIENT_SECRET, | ||
| tenantId: process.env.AZURE_AD_TENANT_ID, | ||
| profile(profile) { | ||
| return Promise.resolve({ | ||
| id: profile.sub || profile.id.toString(), // Handle ID based on provider | ||
| name: profile.name || profile.login || profile.username, | ||
| email: profile.email, | ||
| image: profile.picture || profile.avatar_url || profile.image_url || profile.image, | ||
| role: "USER", | ||
| }); | ||
| }, | ||
| }), | ||
| CredentialsProvider({ |
There was a problem hiding this comment.
remove all unused code.
also, i would prefer if we could incorporate this into the custom oauth adapter. I dont want to add code for all providers out there.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Al that is needed are the following environment variables:
AZURE_AD_CLIENT_ID=
AZURE_AD_CLIENT_SECRET=
AZURE_AD_TENANT_ID=
ALLOW_DANGEROUS_EMAIL_LINKING=true (Somehow it doesnt work without this)
OAUTH_EXCLUSIVE_LOGIN=true (Shows only Sign in with Azure AD button)