This project has adopted the Microsoft Open Source Code of Conduct. For more information, see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.
With this version the starter pack now contains localization policy file TrustFrameworkLocalization.xml. The localization policy allows your policy to accommodate different languages to suit your customer needs. For more information, check the PR #107.
The new localization policy is located between the base and the extension policies:
| Policy | Base policy | Notes |
|---|---|---|
| B2C_1A_TrustFrameworkBase | 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. | |
| B2C_1A_TrustFrameworkLocalization | B2C_1A_TrustFrameworkBase | Holds the localization strings. |
| B2C_1A_TrustFrameworkExtensions | B2C_1A_TrustFrameworkLocalization | Holds the unique configuration changes for your tenant. |
| Relying Parties (RP) | B2C_1A_TrustFrameworkExtensions | For example: sign-up, sign-in, password reset, or profile edit. |
To migrate from the older version of the starter pack to this version:
-
Download the starter pack and update the tenant name.
-
Upload the newer version of TrustFrameworkBase.xml file.
-
Upload the new TrustFrameworkLocalization.xml file.
-
Update your existing TrustFrameworkExtension.xml with the new base policy
B2C_1A_TrustFrameworkLocalization. The following XML snippet demonstrates the base policy before the change:<!-- file: TrustFrameworkExtensions.xml --> <BasePolicy> <TenantId>yourtenant.onmicrosoft.com</TenantId> <PolicyId>B2C_1A_TrustFrameworkBase</PolicyId> </BasePolicy>
The following XML snippet demonstrates the base policy after the change:
<!-- file: TrustFrameworkExtensions.xml --> <BasePolicy> <TenantId>yourtenant.onmicrosoft.com</TenantId> <PolicyId>B2C_1A_TrustFrameworkLocalization</PolicyId> </BasePolicy>
-
Upload the TrustFrameworkExtension.xml policy.
Update to the content definition page version. With the new version the starter pack uses the page contract. For more information, see Migrating to page layout.
Updated policies to use the new Ocean Blue template
A collection of bugfixes, improvements to code, and additional feature support is included in this starterpack. It is not necessary or encouraged for developers to change policies currently in production or in testing. We do encourage the use of these new versions for all new projects.
Public Preview Release
Added Key definition to the metadata element in all four TrustframeworkBase.xml versions. When this Item Key is set to TRUE, the expiration dates on the token issued by B2C will be presented as JSON Numbers. When set to False (default) they will be presented as strings.
<Item Key="SendTokenResponseBodyWithJsonNumbers">true</Item> The following Change is incorporated into the latest version of starterpack (01/29/2019) - It remains here for historical purposes. 06/26/2017 - Correction to SocialAndLocalAccountswMFA in TrustFrameworkBase.xml file.
A change to fix a data loss issue related to SSO, the profile edit policy, and MFA. This issue was due to the MFA SSO technical profile not outputting the below claim in the same format that the regular MFA provider does
<TechnicalProfile Id="SM-MFA">
<DisplayName>Session Mananagement Provider</DisplayName>
<Protocol Name="Proprietary" Handler="Web.TPEngine.SSO.DefaultSSOSessionProvider, Web.TPEngine, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null" />
<PersistedClaims>
***OLD: <PersistedClaim ClaimTypeReferenceId="strongAuthenticationPhoneNumber" />
***CORRECTED: <PersistedClaim ClaimTypeReferenceId="Verified.strongAuthenticationPhoneNumber" />
<PersistedClaim ClaimTypeReferenceId="executed-PhoneFactor-Input" />
</PersistedClaims>
<OutputClaims>
<OutputClaim ClaimTypeReferenceId="isActiveMFASession" DefaultValue="true" />
</OutputClaims>
</TechnicalProfile>