Troubleshooting Azure AD B2C Sign-in Errors: Resolving the 'Server Error in '/' Application'

Table of Contents

Symptoms¶

When attempting to sign up for or sign in to an application configured for Microsoft Azure B2C (Business to Consumer), you might encounter a frustrating error message. This error typically manifests as a “Server Error in ‘/’ Application” within your web browser. Accompanying this general server error, you will likely see a more specific message indicating a “404 (Not Found)” response status code. This combination of errors points to an issue preventing the application from correctly communicating with the Azure B2C service.

The detailed error description further elaborates on the problem, stating: “An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.” The exception details reveal a System.Net.WebException with the message: “The remote server returned an error. 404 (Not Found)”. This indicates that the application is attempting to reach a resource on the Azure B2C server, but that resource cannot be found at the specified address.

The source error, often pinpointed within the application’s code, may highlight lines similar to the following, particularly within authentication-related logic:

Line 106: {
Line 107: ...
Line 108: OpenIdConnectConfiguration config = await mgr.GetConfigurationAsync();
Line 109: ...
Line 110: }

This code snippet suggests that the application is failing to retrieve the OpenID Connect configuration from Azure B2C. The GetConfigurationAsync() method, responsible for fetching this crucial configuration, is throwing a 404 error, meaning the endpoint it is trying to access is not found. This failure prevents the sign-in or sign-up process from completing successfully, leaving users unable to access the application.

Cause¶

The root cause of this “Server Error in ‘/’ Application” with a 404 (Not Found) status code in the context of Azure AD B2C sign-in is often traced back to the configuration of your application’s web.config file. Specifically, this issue arises when the Policy Name settings for critical Azure B2C functionalities are either missing or incorrectly configured. These functionalities include sign-in, password reset, and user profile management.

Azure B2C relies on policies to define and control user experiences for common identity tasks. These policies are configured within the Azure portal and are identified by unique names. Your application needs to be informed about these policy names to correctly interact with Azure B2C. This is achieved by specifying these policy names in your application’s configuration, typically within the web.config file for .NET applications.

The web.config file acts as a central repository for application settings, including connection strings, application keys, and custom configurations. Within this file, specific app keys are designated to hold the policy names required for Azure B2C integration. If these keys are missing, misspelled, or contain incorrect policy names that do not match those defined in your Azure B2C tenant, the application will fail to locate the necessary configuration endpoints when attempting to perform sign-in, password reset, or profile management operations. Consequently, the application will generate a 404 error as it attempts to access non-existent resources based on the faulty policy name configurations.

Resolution¶

To effectively resolve the “Server Error in ‘/’ Application” and the underlying 404 (Not Found) error during Azure AD B2C sign-in, you need to carefully examine and rectify the policy name configurations within your application’s web.config file. The resolution process involves a systematic check and correction of specific application settings to ensure they accurately reflect the policy names defined in your Azure B2C tenant.

Follow these steps to address the issue:

1. Locate and Open the web.config file: The first step is to find the web.config file associated with your application. This file is typically located in the root directory of your web application project. Use a text editor or an IDE like Visual Studio to open the web.config file. Ensure you have appropriate permissions to modify this file.

2. Verify Policy Name App Keys: Within the web.config file, navigate to the <appSettings> section. This section contains key-value pairs that define application-specific settings. You need to verify the existence and correctness of the following app keys related to Azure B2C policies:

   • ida:SignInPolicyId: This app key is crucial for the sign-in policy. Ensure that this key exists and that its value is exactly the name of the Sign-in policy you configured within the Azure B2C Admin Portal. Double-check for any typos or incorrect casing.

   • ida:PasswordResetPolicyId: This app key is essential for the password reset policy. Verify that this key is present and that its value accurately matches the name of the Password Reset policy you defined in the Azure B2C Admin Portal. Again, pay close attention to spelling and capitalization.

   • ida:UserProfilePolicyId: This app key is used for the user profile editing policy. Confirm that this key exists and that its value correctly corresponds to the name of the User Profile policy you set up in the Azure B2C Admin Portal. Accuracy in naming is paramount.

   For each of these app keys, carefully compare the value in your web.config file with the actual policy name in your Azure B2C portal. They must be an exact match for the application to correctly locate and utilize the defined policies.

3. Example web.config Configuration: The <appSettings> section of your web.config file should resemble the following structure, with the correct policy names substituted for the placeholder values:

   <appSettings>
   ...
   <add key="ida:SignInPolicyId" value="B2C_Signin_Policy" />
   <add key="ida:PasswordResetPolicyId" value="B2C_PasswordReset_Policy" />
   <add key="ida:UserProfilePolicyId" value="B2C_UserProfile_Policy" />
   ...
   </appSettings>
   

   Important Considerations:

   • Policy Name Accuracy: The values assigned to ida:SignInPolicyId, ida:PasswordResetPolicyId, and ida:UserProfilePolicyId in your web.config file must precisely match the names of the corresponding policies configured in your Azure B2C tenant. Any discrepancy, even a minor typo, will lead to the 404 error.

   • Azure B2C Portal Verification: Always cross-reference the policy names in your web.config file with the policy names displayed in the Azure B2C Admin Portal. This ensures that you are using the correct and up-to-date policy identifiers.

   • Application Restart: After modifying the web.config file, you may need to restart your application or web server for the changes to take effect. This ensures that the application re-reads the configuration and uses the corrected policy names.

By meticulously following these steps and ensuring the accuracy of your policy name configurations in the web.config file, you can effectively resolve the “Server Error in ‘/’ Application” and enable seamless sign-in and sign-up experiences for your users within your Azure B2C integrated application.

---

Have you encountered this Azure AD B2C error before? What troubleshooting steps did you take? Share your experiences and tips in the comments below!