providers/azure-ad
default()β
default<
P
>(options
):OAuthConfig
<P
>
Add AzureAd login to your page.
Setupβ
Callback URLβ
https://example.com/api/auth/callback/azure-ad
Configurationβ
import Auth from "@auth/core"
import AzureAd from "@auth/core/providers/azure-ad"
const request = new Request(origin)
const response = await Auth(request, {
providers: [AzureAd({ clientId: AZURE_AD_CLIENT_ID, clientSecret: AZURE_AD_CLIENT_SECRET })],
})
Resourcesβ
Type parametersβ
βͺ P extends AzureADProfile
Parametersβ
βͺ options: OAuthUserConfig
<P
> & object
Returnsβ
OAuthConfig
<P
>
Exampleβ
To allow specific Active Directory users access:β
- In https://portal.azure.com/ search for "Azure Active Directory", and select your organization.
- Next, go to "App Registration" in the left menu, and create a new one.
- Pay close attention to "Who can use this application or access this API?"
- This allows you to scope access to specific types of user accounts
- Only your tenant, all azure tenants, or all azure tenants and public Microsoft accounts (Skype, Xbox, Outlook.com, etc.)
- When asked for a redirection URL, use
https://yourapplication.com/api/auth/callback/azure-ad
or for developmenthttp://localhost:3000/api/auth/callback/azure-ad
. - After your App Registration is created, under "Client Credential" create your Client secret.
- Now copy your:
- Application (client) ID
- Directory (tenant) ID
- Client secret (value)
In .env.local
create the following entries:
AZURE_AD_CLIENT_ID=<copy Application (client) ID here>
AZURE_AD_CLIENT_SECRET=<copy generated client secret value here>
AZURE_AD_TENANT_ID=<copy the tenant id here>
That will default the tenant to use the common
authorization endpoint. For more details see here.
Azure AD returns the profile picture in an ArrayBuffer, instead of just a URL to the image, so our provider converts it to a base64 encoded image string and returns that instead. See: https://docs.microsoft.com/en-us/graph/api/profilephoto-get?view=graph-rest-1.0#examples. The default image size is 48x48 to avoid running out of space in case the session is saved as a JWT.
In pages/api/auth/[...nextauth].js
find or add the AzureAD
entries:
import AzureADProvider from "next-auth/providers/azure-ad";
...
providers: [
AzureADProvider({
clientId: process.env.AZURE_AD_CLIENT_ID,
clientSecret: process.env.AZURE_AD_CLIENT_SECRET,
tenantId: process.env.AZURE_AD_TENANT_ID,
}),
]
...
Notesβ
By default, Auth.js assumes that the AzureAd provider is based on the OAuth 2 specification.
The AzureAd provider comes with a default configuration. To override the defaults for your use case, check out customizing a built-in OAuth provider.
If you think you found a bug in the default configuration, you can open an issue.
Auth.js strictly adheres to the specification and it cannot take responsibility for any deviation from the spec by the provider. You can open an issue, but if the problem is non-compliance with the spec, we might not pursue a resolution. You can ask for more help in Discussions.