You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It looks like both Azure Entra and Zure AD provider no longer accept tenant ID
This is my config
import AzureADProvider from "next-auth/providers/microsoft-entra-id";
AzureADProvider({
name: "Organisation - Staff",
id: "staff",
clientId: env.STAFF_AZURE_CLIENT_ID,
clientSecret: env.STAFF_AZURE_CLIENT_SECRET,
tenantId: env.STAFF_AZURE_TENANT_ID, // <=== WILL BE ERROR
}),
Consequently, it seems that the tenant ID is being sent to azure as "common", and not rerquired STAFF_AZURE_TENANT_ID.
This leads to the following error coming from Azure:
Application '{appId}'({appName}) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '{time}'. Use a tenant-specific endpoint or configure the application to be multi-tenant.
How to reproduce
Add the AzureADProvider with the backend not supporting Multi-Tenancy applications and requiring tenantId
You can fix this by downgrading to next-auth 5.0.0-beta.22
Expected behavior
The "tenantId" should exist and be supported as per documentation at:
Provider type
Azure Active Directory
Environment
Reproduction URL
https://github.com/tomitrescak/next-auth-azure-ad-error
Describe the issue
It looks like both Azure Entra and Zure AD provider no longer accept tenant ID
This is my config
Consequently, it seems that the tenant ID is being sent to azure as "common", and not rerquired
STAFF_AZURE_TENANT_ID
.This leads to the following error coming from Azure:
How to reproduce
Add the AzureADProvider with the backend not supporting Multi-Tenancy applications and requiring tenantId
You can fix this by downgrading to
next-auth 5.0.0-beta.22
Expected behavior
The "tenantId" should exist and be supported as per documentation at:
https://authjs.dev/getting-started/providers/azure-ad
The text was updated successfully, but these errors were encountered: