CODEWITHSUNDEEP
azure-ad-b2cazure-ad-b2c-custom-policy
GTRekter
GTRekter

Reputation: 1007

Unable to translate error message in AD B2C custom policy "Unable to validate the information provided."

We are using AD B2C custom policies for our sign-in flows and we are also doing language customization.

Even if it's possible to localize the error messages using custom policies (https://learn.microsoft.com/en-us/azure/active-directory-b2c/localization-string-ids), for example:

<LocalizedResources Id="api.localaccountsignup.en">
  <LocalizedStrings>
    <LocalizedString ElementType="ErrorMessage" StringId="DefaultUserMessageIfRequestFailed">Failed to establish connection to restful service end point.</LocalizedString>
    <LocalizedString ElementType="ErrorMessage" StringId="UserMessageIfCircuitOpen">Unable to connect to the restful service end point.</LocalizedString>
    <LocalizedString ElementType="ErrorMessage" StringId="UserMessageIfDnsResolutionFailed">Failed to resolve the hostname of the restful service endpoint.</LocalizedString>
    <LocalizedString ElementType="ErrorMessage" StringId="UserMessageIfRequestTimeout">Failed to establish connection to restful service end point within timeout limit.</LocalizedString>
  </LocalizedStrings>
</LocalizedResources>

I cannot find a key for the message "Unable to validate the information provided."

enter image description here

Also, it doesn't have an ID.

enter image description here

Upvotes: 1

Views: 662

Answers (1)

Jas Suri - MSFT
Jas Suri - MSFT

Reputation: 11315

You cannot customise this error as this occurs when the actual policy has been configured in such a way that it cannot actually handle the users page submission. It indicates your policy has a bug in its logic.

You should troubleshoot why this error is occurring: https://learn.microsoft.com/en-us/azure/active-directory-b2c/troubleshoot?pivots=b2c-user-flow

One of the validation technical profiles during the sign in technical profile is problematic.

This error will never be displayed to a user with a policy that’s configured to handle all scenarios the can force. Hence there is no localisation available or needed for this error.

Upvotes: 3

Related Questions