Test App Service Authentication on localhost

Question

Test App Service Authentication on localhost

Shuo-Yang Wang 0

I set up Facebook Authentication on my web service and added 127.0.0.1:3000/<my_path> to "Allowed external redirect URLs". The prod works fine and I can get authenticationToken in the returned URI fragment. Therefore, I tried to do the similar thing in localhost, I first hit https://<my_domain>/.auth/login/facebook?post_login_redirect_uri=https://127.0.0.1:3000/<my_path> in the browser bar and get authenticationToken successfully. However, when redirecting from a link in my page <a href="https://<my_domain>/.auth/login/facebook?post_login_redirect_uri=https://127.0.0.1:3000/<my_path>">link</a>, there is no authenticationToken returned.

Setting:

Screen Shot 2023-08-30 at 9.31.50 PM

Prod:

Screen Shot 2023-08-30 at 9.19.04 PM

Localhost redirecting from browser bar:

Screen Shot 2023-08-30 at 9.28.25 PM

Localhost redirecting from a link in my page:

Screen Shot 2023-08-30 at 9.24.21 PM

What's the difference between entering the login flow from browser bar and redirecting from a link? How should I test login flow locally?

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-08-31T19:11:31.3+00:00

Based on my understanding of your issue description, it seems like you are trying to authenticate with Facebook on your web service and you have set up the allowed external redirect URLs to include 127.0.0.1:3000/<my_path> for your local development environment.

When you hit the URL https://<my_domain>/.auth/login/facebook?post_login_redirect_uri=https://127.0.0.1:3000/<my_path> directly in the browser, you are able to get the authentication token successfully. However, when you try to redirect from a link in your page, you are not getting the authentication token.

This could be because the link in your page is not using the correct URL format for the authentication request. Make sure that the link in your page is using the correct URL format for the authentication request.

When you enter the login flow from the browser bar, you are directly hitting the authentication URL and initiating the authentication flow. When you redirect from a link in your page, you are relying on the browser to correctly handle the redirect and initiate the authentication flow.

The difference between these two methods is that when you enter the login flow from the browser bar, you have more control over the URL and can ensure that it is correctly formatted. When you redirect from a link in your page, you need to make sure that the link is correctly formatted and that the browser is handling the redirect correctly.

checkout : The difference between these two methods is that when you enter the login flow from the browser bar, you have more control over the URL and can ensure that it is correctly formatted. When you redirect from a link in your page, you need to make sure that the link is correctly formatted and that the browser is handling the redirect correctly. Please checkout this doc for more info.

Kindly let us know if I misunderstood your scenario, if you are still having issues, please provide more info about your requirement and, configuration and the steps you have taken so far.

Shuo-Yang Wang 0

I checked the URL format and confirmed that the URLs are the same. Please see the video recording: https://1drv.ms/v/s!Ao51QBapsdZys3_MTYImyUc55eWs?e=U9lRKh

My setting from troubleshoot panel:

{
"enabled": True,
"runtimeVersion": ,
"unauthenticatedClientAction": "AllowAnonymous",
"tokenStoreEnabled": True,
"allowedExternalRedirectUrls": ,
"defaultProvider": ,
"clientId": "================================",
"clientSecret": ,
"clientSecretCertificateThumbprint": ,
"issuer": "https://login.microsoftonline.com/consumers/v2.0",
"allowedAudiences": "[]",
"isAadAutoProvisioned": False,
"googleClientId": "==========================================.apps.googleusercontent.com",
"googleClientSecret": ,
"googleOAuthScopes": ,
"facebookAppId": "==================",
"facebookAppSecret": ,
"facebookOAuthScopes": "[
  "email",
  "public_profile"
]",
"twitterConsumerKey": ,
"twitterConsumerSecret": ,
"microsoftAccountClientId": ,
"microsoftAccountClientSecret": ,
"microsoftAccountOAuthScopes": ,
"openIdConnectProviders": ""{}""
}

In addition, this also happens in Google and Microsoft login flows. Is there a way to see the http logs of the built-in authentication middleware service?

ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-09-03T07:41:57.2733333+00:00

Apologies for the delay from over the weekend.
Thanks for the follow-up and additional info. I'm following-up on this shortly.

1 answer

Your answer

Shuo-Yang Wang 0 Reputation points

2023-09-01T02:35:57.9366667+00:00

I checked the URL format and confirmed that the URLs are the same. Please see the video recording: https://1drv.ms/v/s!Ao51QBapsdZys3_MTYImyUc55eWs?e=U9lRKh

My setting from troubleshoot panel:

{ "enabled": True, "runtimeVersion": , "unauthenticatedClientAction": "AllowAnonymous", "tokenStoreEnabled": True, "allowedExternalRedirectUrls": , "defaultProvider": , "clientId": "================================", "clientSecret": , "clientSecretCertificateThumbprint": , "issuer": "https://login.microsoftonline.com/consumers/v2.0", "allowedAudiences": "[]", "isAadAutoProvisioned": False, "googleClientId": "==========================================.apps.googleusercontent.com", "googleClientSecret": , "googleOAuthScopes": , "facebookAppId": "==================", "facebookAppSecret": , "facebookOAuthScopes": "[ "email", "public_profile" ]", "twitterConsumerKey": , "twitterConsumerSecret": , "microsoftAccountClientId": , "microsoftAccountClientSecret": , "microsoftAccountOAuthScopes": , "openIdConnectProviders": ""{}"" }

In addition, this also happens in Google and Microsoft login flows. Is there a way to see the http logs of the built-in authentication middleware service?
ajkuma 28,036 Reputation points Microsoft Employee Moderator

2023-09-03T07:41:57.2733333+00:00

Apologies for the delay from over the weekend.
Thanks for the follow-up and additional info. I'm following-up on this shortly.

Answer 1

Shuo-Yang Wang,

Edit:
Logging for App Service auth should work by setting FileSystem logging to Verbose - Logging and tracing, and see if this provides some pointers.

Kindly let us know how this goes, we can also engage with you further offline.

Apologies for the delay on this, we wish to engage with you offline for a much closer look, please send an email with subject line “Attn:Ajay” to AzCommunity[at]Microsoft[dot]com with the following details, I will follow-up with you.

1. Referencing this thread,

2. Azure subscription ID,

3. Azure resource name and the time of issue occurrence.

If the answer helped (pointed, you in the right direction) > please click Accept Answer

Share via

Test App Service Authentication on localhost

1 answer

Your answer