active-directory-aspnetcore-webapp-openidconnect-v2 VS next-auth

See also the Azure AD ID token claims reference for fields you can expect to see in the decoded ID token, as well as this ASP.NET Example that talks about how to configure Azure to provide the roles/group membership info in its ID tokens.

First of all, register an application in your Azure portal. You will need so called "Tenant ID" and "Client ID". Use this sample project with the detailed instruction what to do: Enable your ASP.NET Core web app to sign in users and call Microsoft Graph with the Microsoft identity platform

Please upvote this issue https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/issues/664

API - Azure AD

The official repo at https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2 is probably the most up-to-date. For example if you want B2C then https://github.com/Azure-Samples/active-directory-aspnetcore-webapp-openidconnect-v2/tree/master/4-WebApp-your-API/4-2-B2C The example they have should work with .NET 6

I was having this exact issue a few days ago and found the same thread. I wasn't using Blazor and had to keep clearing my cookies to get around it. I think I updated microsoft.identity.web.ui package and it resolved itself (to 1.16).

Permissions in your application can be aligned to custom groups in your customers' AAD tenants. There are several ways to retrieve the group information. You can get the user's groups in the token. Or you could also ping Microsoft Graph to get the Groups the customer is a member of. There are few things to think about with groups:

NextAuth.js is not perfect. One of the shortcomings is that it currently does not implement federated logout. This means that even if a user signs out of the Next.js app, he does NOT get signed out of the Cognito user pool client. As a consequence, the user is not really being logged out (i.e he is able to login again without providing the credentials). You can read more about this problem in this Github thread.

NextAuth for adding auth

Let's learn a bit about Descope and how to use it with Auth.js (next-auth) to protect our Next.js app with role-based access control (RBAC).

https://github.com/nextauthjs/next-auth/issues/5647#issuecom...

Next Auth CognitoProvider Internal Library: https://github.com/nextauthjs/next-auth/blob/v4/packages/next-auth/src/providers/cognito.ts

I mentioned this in an age-old discussion on NextAuth GitHub repo.

Authentication is a fundamental part of most web applications. Integrating authentication into your Next.js app can be simplified with NextAuth, a powerful authentication library that supports various authentication methods. However, the documentation around setting up NextAuth with the "Credentials" auth provider might not be as clear as you'd hope. My implementation is greatly enriched and partially based on Next-Auth docs and the following github thread.

For Auth: https://authjs.dev/ - works like a charm with Svelte https://authjs.dev/reference/sveltekit

NextAuth.js

I'm surprised nobody mentioned https://authjs.dev/