CODEWITHSUNDEEP
azureazure-active-directoryazure-web-app-servicesingle-sign-onhttp-status-code-502
DevSoftUK
DevSoftUK

Reputation: 1

Azure single sign on 502 bad gateway

We are facing 502 bad gateway error on web portal which uses our client Azure App registration settings.

Client provided us the following details with single username / password form their domanin to test SSO

"AzureAd": {
    "Instance": "https://login.microsoftonline.com/",
    "Domain": "XXXXX.co.uk",
    "TenantId": "xxxxxxxxx-xxxx-xxxx-xxx-xxxxxxxxxxxx",
    "ClientId": "xxxxxxxxx-xxxx-xxxx-xxx-xxxxxxxxxxxx",
    "CallbackPath": "/SignInVerify",
    "SignOutPath": "/aad-signout"
  }

We deployed website, tested everything using the user provided and all seems to be working for user client provided.

When more user tried to use this website, they get 502 bad gateway erorr but we can still use username/password provided to us without any issue.

Client is large corporate client could have multiple Azure tenant for Azure Active Directory and we don't know their user group structure etc.

What could be the cause of the issue for all user other than the one we can currnetly test/use?

Thank you for your help in advance on this.

Upvotes: 0

Views: 2510

Answers (1)

Harshitha Veeramalla
Harshitha Veeramalla

Reputation: 1753

Change the configuration to below format :

{  
"AzureAd": {  
"Instance": "[https://login.microsoftonline.com/"](https://login.microsoftonline.com/%22 "https://login.microsoftonline.com/%22"),  
"Domain": "microsoft.onmicrosoft.com",  
"TenantId": "xxxxxxxxxxxxxxxxxxxx",  
"ClientId": "xxxxxxxxxxxxxxxxxxxx",  
"CallbackPath": "/signin-oidc",  
"SignedOutCallbackPath": "/signout-callback-oidc"  
},

And also check that you have selected multitenant

enter image description here

Upvotes: 0

Related Questions