Adding localization

[yoelhor]

Adding localization to the custom policy starter pack

login-NonInteractive

The following metadata elements have been moved to the localization policy:

<Item Key="UserMessageIfClaimsPrincipalDoesNotExist">We can't seem to find your account</Item>
<Item Key="UserMessageIfInvalidPassword">Your password is incorrect</Item>
<Item Key="UserMessageIfOldPasswordUsed">Looks like you used an old password</Item>

The following metadata comment out. You may use it with conditional access.

<Item Key="grant_type">password</Item>

SignUpWithLogonEmailExchange

The self-asserted technical profile uses the new api.localaccountsignin content definition, instead of the generic one api.selfasserted. This change allows you to provide localization strings that are related only to the local account sign-in page.

SelfAsserted-Social

The self-asserted technical profile uses the new api.socialccountsignup content definition instead of the generic one api.selfasserted. This change allows you to provide localization strings that are related only to the social account sign-up page.

AAD-UserReadUsingEmailAddress

The following metadata element has been moved to the localization policy:

<Item Key="UserMessageIfClaimsPrincipalDoesNotExist">An account could not be found for the provided user ID.</Item>

AAD-UserReadUsingAlternativeSecurityId

The following metadata element has been moved to the localization policy:

<Item Key="UserMessageIfClaimsPrincipalDoesNotExist">User does not exist. Please sign up before you can sign in.</Item>

AAD-UserWriteUsingAlternativeSecurityId

The following metadata element has been moved to the localization policy:

<Item Key="UserMessageIfClaimsPrincipalAlreadyExists">You are already registered, please press the back button and sign in instead.</Item>

LocalAccountSignUpWithLogonEmail

The following metadata element has been moved to the localization policy:

<Item Key="language.button_continue">Create</Item>

LocalAccountDiscoveryUsingEmailAddress

The following metadata element has been removed:

<Item Key="UserMessageIfClaimsTransformationBooleanValueIsNotEqual">Your account has been locked. Contact your support person to unlock it, then try again.</Item>

TrustFrameworkExtensions.xml

The extensions policies base policy have been change from B2C_1A_TrustFrameworkBase to B2C_1A_TrustFrameworkLocalization.

The new inheritance model

The new localization policy is located between the base and the extension:

1. The B2C_1A_TrustFrameworkBase file that contains most of the definitions. To help with troubleshooting and long-term maintenance of your policies, try to minimize the number of changes you make to this file.
2. The B2C_1A_TrustFrameworkLocalization holds the localization strings. This policy file is derived from the B2C_1A_TrustFrameworkBase file. Use this file to change the localization strings.
3. An B2C_1A_TrustFrameworkExtensions file that holds the unique configuration changes for your tenant. This policy file is derived from the B2C_1A_TrustFrameworkLocalization file. Use this file to add new functionality or override existing functionality. For example, use this file to federate with new identity providers.
4. The Relying Party (RP) file that is the single task-focused file that is invoked directly by the relying party application, such as your web, mobile, or desktop applications. Each unique task, such as sign-up, sign-in, password reset, or profile edit, requires its own relying party policy file. This policy file is derived from the B2C_1A_TrustFrameworkExtensions file.