Azure AD B2C: Custom Policy Error Related to msal - azure-ad-b2c

I have implemented azure active directory B2C in one of my projects.
I have used the following technology stack for that :
.Net Core 3.1 WEB API
Entity Framework
Angular 8.
Currently, Azure AD B2C is working fine for authentication in the local environment. but it throws me an error in a dev environment when we renew the token.
I have attached a screenshot here.
it would be great if anyone helps me for this.
Thanks

Thanks Karan and please use this sample - https://github.com/Azure-Samples/active-directory-b2c-dotnetcore-webapp and make sure you are using app.UseAuthentication(); in Startup.cs file to avoid the 404 error.
Please let us know if still issue persists.

Related

Azure App Service - Fail after enabling Authentication

We have an app which get data from Azure DevOps Services using RestAPI with token. Without authentication it is working fine.
After enabling authentication get errors 500/431 without any explanation. Authentication set for single tenant and with new application registration.
THE ONLY WAY TO GET AROUND THIS PROBLEM WAS TO USE A CONTAINER BUILD FROM AZURE - USE VS CODE TO PUBLISH & BUILD - USING A CUSTOM CONTAINER FAILED ALWAYS
I tried the following without success:
Setting - WEBSITE_AUTH_DISABLE_IDENTITY_FLOW - Azure Web App + Node.js + Azure AD = Error 431
Added specific permission for - Azure DevOps Services on the Identity provider tab.
Any advice would be most appreciated
The error 500 may occur if you have enabled App Insights monitoring on client-side.
Please check whether you have enabled that option or not like below:
APPINSIGHTS_JAVASCRIPT_ENABLE = true
If it is enabled, disable it by assigning false parameter as suggested in this SO Thread by L. González.
These 500/431 errors occur due to many reasons and to know the exact issue behind the error, try enabling diagnostic logging.
To know more about diagnostic logging please refer this MsDoc
Try restarting the App Service and raise Azure Support Ticket if still the issue persists.
Reference:
how do I fix the azure web app error 500? - Stack Overflow

Getting a 500 error in the redirect Url https://[mydomain.com]/signin-oidc from Azure AD in ASP.Net Core app

I'm getting a 500 error as a result of the /signin-oidc redirect Url to our ASP.Net Core app host ( https://[mydomain.com]/signin-oidc ) from Azure AD.
I'm perplexed that this error started to come up only recently.
This ASP.net Core app using Azure AD Identity for Authenticatication has been running without this 500 error for a couple months.
We haven't made any change to either our ASP.Net Core app or the settings in Azure AD for our app services.
Would appreciate any tip or suggestion on trouble-shooting and resolving this error.
For this issue, I think you need to contact the Azure support team for assistance.
You can raise a support ticket on azure portal by following this link.

You do not have permission to view this directory or page

I have created a new MVC application with windows authentication and without doing any changes to application, I have deployed to Azure App Service.
When I browse the URL I am getting the message as "You do not have permission to view this directory or page.".
When I check the "DetailedErrors" folder, it was "IIS Detailed Error - 401.0 - Unauthorized".
I have referred many post with this issue. But none of the solution mentioned in the post solved my issue.
Please let me know what configuration I am missing.
Thanks
Windows authentication is not supported in App Service.
In order for IWA to work, the server would need to be AD joined.
You do not have that level of access in App Service.
https://devblogs.microsoft.com/premier-developer/moving-legacy-asp-net-apps-with-windows-authentication-to-azure-app-service-part-1/
You will have to migrate to e.g. Azure AD authentication or host the app on a platform that supports IWA.

Azure Web Application Raising Internal Server Error when talking to API Web Application

I have an solution that consists of a web gui front end and a web api backend. Both use Azure AD for auth with the former passing a token to the latter.
This all works fine on both a localhost and an OnPrem server, but when I push the release to Azure, I get a 500 Internal Server error when the GUI attempts to utilise the API.
At the moment, I am unable to obtain any further error detail.
I know this is a little vague, but I am pretty new to the whole Azure platform and am unsure how to diagnose the issue further.
Any assistance or pointers that people can give would be greatly appreciated.
Cheers
I know this is a little vague, but I am pretty new to the whole Azure platform and am unsure how to diagnose the issue further.
Per my understanding, you could follow the steps below to troubleshoot this issue:
For .NET web application, you could add customErrors flag in the Web.config file and set the value to On or RemoteOnly to see the detailed error message. Also, you could enable diagnostics logging for web apps to retrieve more details about the error message. Or you could just leverage Remote debugging web apps for a simple way to locate the specific issue. For more details, you could follow this official tutorial about troubleshooting azure web apps.
For .NET Core web application, you could refer to this similar issue. Additionally, for php, you could refer to nfo About PHP Fatal Error and Error Log on Azure Website and Change the built-in PHP configurations to troubleshoot this issue.

Azure Multi Factor Authentication Mobile App Error

I am trying to configure MFA using Azure MFA. Its all working correctly apart from getting the following error in the Mobile App when scanning a QR code (adding manually produces the same error):
The web service looks to be configured correctly:
https://mfa.optimisemedia.com/MultiFactorAuthMobileAppWebService/pfpaws.asmx
And the Web Service SDK:
https://mfa.optimisemedia.com/MultiFactorAuthWebServiceSdk/
Any help greatly appreciated as I've come up against a brick wall now.
It seems the problem was down to IIS permissions. The installer doesn't set these correctly.
More info can be found at https://dirteam.com/sander/2015/03/27/knowledgebase-you-receive-a-web-service-requests-must-be-protected-by-authentication-error-when-activating-a-multi-factor-auth-app/

Resources