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
OPError: invalid_tenant (AADSTS90002: Tenant 'organizations' not found. This may happen if there are no active subscriptions for the tenant. Check with your subscription administrator.
Trace ID: 300590d6-2a8e-4c83-9f3f-db557c283800
Correlation ID: a93061b7-384f-4bb9-ab75-78d12cb062ff
Timestamp: 2019-07-12 05:23:38Z)
at processResponse (C:/Users/.../node_modules/openid-client/lib/helpers/process_response.js:39:13)
at C:/Users/.../node_modules//openid-client/lib/issuer.js:241:20
at async C:/Users/.../node_modules/p-some/index.js:82:19
OPError: expected 200 OK, got: 404 Not Found
at processResponse (C:/Users/.../node_modules/openid-client/lib/helpers/process_response.js:42:11)
at C:/Users/.../node_modules/openid-client/lib/issuer.js:241:20
at async C:/Users/.../node_modules/p-some/index.js:82:19
https://login.microsoftonline.com/organizations is 100% invalid and the error you're getting comes from microsoft, echoed by this library.
https://login.microsoftonline.com/organizations/v2.0 works but will likely need a patch similar to common to allow the Azure AD multi-tenancy issuer validation relaxed.
Describe the bug
Attempting to use the authority https://login.microsoftonline.com/organizations results in the following error.
Changing the authority to https://login.microsoftonline.com/common fixes the issue. Both authorities work with MSAL.js.
To Reproduce
Issuer and Client configuration: (inline or gist) - Don't forget to redact your secrets.
Expected behaviour
The "organizations" tenant should be usable as documented at MSDN.
Environment:
openid-client version: 3.2.1
node version: 12.0.0 (Electron 6.0.0-beta.13)
the bug is happening on latest openid-client too.
i have searched the issues tracker on github for similar issues and couldn't find anything related.
The text was updated successfully, but these errors were encountered: