Azure Web App Authentication / Authorization issue

2
votes

I am trying to authenticate my Azure Web App. Follow this doc

In my Azure Portal, I've selected "Authenticate / Authorization" for my Web App. After I configure my Microsoft Account Authentication Settings with Client ID/Key from the App Registration page, I save the settings page and I'll see an error: enter image description here The errors says:

Failed to save Auth Settings for WebApp App: {"Code":"Conflict","Message":"Cannot update the site 'WebApp' because Authentication / Authorization was configured with an invalid issuer URL ''. The URL must be well-formed, absolute, and use the HTTPS scheme.","Target":null,"Details":[{"Message":"Cannot update the site 'WebApp' because Authentication / Authorization was configured with an invalid issuer URL ''. The URL must be well-formed, absolute, and use the HTTPS scheme."},{"Code":"Conflict"},{"ErrorEntity":{"ExtendedCode":"04530","MessageTemplate":"Cannot update the site '{0}' because Authentication / Authorization was configured with an invalid issuer URL '{1}'. The URL must be well-formed, absolute, and use the HTTPS scheme.","Parameters":["WebApp",""],"Code":"Conflict","Message":"Cannot update the site 'WebApp' because Authentication / Authorization was configured with an invalid issuer URL ''. The URL must be well-formed, absolute, and use the HTTPS scheme."}}],"Innererror":null}

I'm not sure what's the "invalid issuer URL" the issue is referring to.

3
azureauthenticationazure-web-app-serviceazure-active-directory
Go to apps.dev.microsoft.com and Check if the Redirect URLs in your Application is like this: https://<the URL of your App>/.auth/login/microsoftaccount/callback and the application platform is Web. - Wayne Yang
Yes I did that. - Helen Lo
Even still got the error ? - Wayne Yang
I changed my region to another one and it worked! Thanks @WayneYang-MSFT - Helen Lo
So I republished my app to US West 2, and it works there. This is very bizarre. - Mikeyg36

3 Answers

5
votes

This issue is not a general issue. This article is absolutely correct.

So I suggest you try to use another location to deploy your Web App and configure the Applicaiton again.

Also, this issue should be temporary, I have reported this.

Hope this helps!

5
votes

I'm on the App Service team. This is a known issue which we are working to address - the behavior should be temporary. Our apologies for any issues this has caused.

I do not recommend the solution of moving to another region, as this is not guaranteed to work, and sites that do see resolution in this way may break again.

Please find our recommended workaround instructions in my response to this forum post.

0
votes

For me it worked to add AAD as an auth provider with the default setting even though I'm not using it. I was then able to save my Facebook auth settings. This is a temporary workaround. This answer from this discussion. Edit field "issuer" not working for me.