IIS return 302 code when login with AzureAd

Phi Vuong (from The Enest) 6

I got HTTP status code as 302 in server log IIS when login with AzureAd with Postman and Mobile App

2021-08-09 02:41:10 ..*. GET /api/BaseDDL/GetCourseTypeDDL durationId=2 443 - 171.227.23.201 PostmanRuntime/7.28.3 - 302 0 0 62

The Postman screen and Mobile App received the HTML page like this:

Lex Li (Microsoft) 4,907 Reputation points Microsoft Employee

2021-08-09T06:15:23.613+00:00

When using an authentication method like Azure AD, such 302 responses are expected as the authentication is done on a specific end point and then jump back to your web app. You are not watching the same request/response pair if you are more patient on URLs.
Phi Vuong (from The Enest) 6 Reputation points

2021-08-09T06:32:47.44+00:00

How can I fix it ?
Bruce Zhang-MSFT 3,736 Reputation points

2021-08-09T08:46:12.203+00:00

Hi @Phi Vuong (from The Enest) ,

What do you want to fix? 302 is only a temporary redirection. After a successful login, you can re-visit the original URI as you logged in.
Vinh Pham 6 Reputation points

2021-08-11T01:43:55.497+00:00

Our Web app host in IIS and use login with Azure AD. We can use on browser properly but can not call API from Postman or Mobile App, it's keep returning Login page below, regardless access token I got from Oauth2. How can I fix it, please help.
Will Strege 0 Reputation points

2023-03-14T21:03:57.57+00:00

@Bruce Zhang-MSFT I am running into the same thing when attempting to use powershell or postman to access an Azure AD secured API, redirecting to "https://login.microsoftonline.com/{tenantId}/oauth2/authorize" instead of the endpoint. I get the bearer token and then pass that with the call to the endpoint; it should be authorized. Thanks!