Single-tenant Azure Ad integration error

[Tobias-Holmgrens]

Environment

• Operating System: Windows_NT
• Node Version: v20.17.0
• Nuxt Version: 3.12.4
• CLI Version: 3.12.0
• Nitro Version: 2.9.7
• Package Manager: [email protected]
• Builder: -
• User Config: compatibilityDate, nitro, devtools, imports, modules, ssr, auth, primevue, css, runtimeConfig, plugins, openFetch
• Runtime Modules: @primevue/[email protected], @nuxtjs/[email protected], @pinia/[email protected], [email protected], @sidebase/[email protected]
• Build Modules: -

Reproduction

Setup an Azure App registration as a Single tenant account.
Integrate nuxt-auth as usual against the azure ad provider

AzureADProvider.default({
            clientId: runtimeConfig.azureAdClientId,
            clientSecret: runtimeConfig.AzureAdClientSecret,
            tenantId: runtimeConfig.AzureAdTenantId,
        }),

auth: {
    isEnabled: true,
    globalAppMiddleware: true,
    disableServerSideAuth: false,
    originEnvKey: 'NUXT_AUTH_ORIGIN',
    provider: {
      type: 'authjs',
      trustHost: false,
      defaultProvider: 'azure-ad',
      addDefaultCallbackUrl: true,
    },
  },

Describe the bug

When faced with the microsoft login screen and login is performed error

AADSTS50194: Application 'app guid'(app name) is not configured as a multi-tenant application. Usage of the /common endpoint is not supported for such applications created after '10/15/2018'. Use a tenant-specific endpoint or configure the application to be multi-tenant.

occurs due to the "https://login.microsoftonline.com/common/reprocess" url is called

Additional context

Need settings similar to msal's authority or next-auths authorization. Tried those settings but does not work

AzureADProvider.default({
            clientId: runtimeConfig.azureAdClientId,
            clientSecret: runtimeConfig.AzureAdClientSecret,
            tenantId: runtimeConfig.AzureAdTenantId,
            authorization: {
                url: `https://login.microsoftonline.com/${runtimeConfig.azureAdTenantId}/oauth2/v2.0/authorize`,
                params: { scope: "user.Read" }
            },
            token: `https://login.microsoftonline.com/${runtimeConfig.azureAdTenantId}/oauth2/v2.0/token`,
        }),

Logs

No response

[zoey-kaiser]

Hi @Tobias-Holmgrens 👋

The NextAuth authorization options are available. We use the same provider with the options in one of our projects and have no issues. Without being able to look into your Azure setup this will be difficult to debug.

You are welcome to book a slot with me and we can try and investigate it together, but sadly I don't have any clear suggestions at the moment: https://cal.com/zoeykaiser/sidebase