This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(230.39999999999998, 27%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESF%3C/text%3E%3C/svg%3E)
Dear Microsoft Support Team,
I have successfully integrated an embedded reset password feature following the guidance provided here and here.
While the integration itself is functional, I have encountered an unexpected change in the title and email text filed displayed on the login screen.
Now current login screen appears as follows:
Prior to the integration, the login screen displayed as expected, similar to the desired view shown below:
I have attached the TrustFrameworkExtensions.xml file for your reference.
Could you please provide guidance on how to rectify this issue and revert to the previous expected view? I appreciate your assistance in resolving this matter promptly.
Kind regards,
Ferdinando.
@Sodano, Ferdinando [COMRES/COLDCHAIN/BLU]
I just wanted to check in and see if you had any other questions or if you were able to resolve this issue?
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.
@Sodano, Ferdinando [COMRES/COLDCHAIN/BLU]
I just wanted to check in and see if you had any other questions?
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.
@Sodano, Ferdinando [COMRES/COLDCHAIN/BLU]
Thank you for your post and I'm glad that you were able to successfully integrate and embed the password reset feature!
To hopefully help point you in the right direction when it comes to your login screen displaying the incorrect text, I'll share my findings below.
Findings:
After reviewing your TrustFrameworkExtensions.xml, I noticed that you're customizing your B2C UI using HTML templates located within your Azure Blob storage account - adb2ccustompagesdev. In order to restore your login page to its original formatting, you should be able to modify the HTML document located within adb2ccustompagesdev.
From the ContentDefinition element "api.signuporsignin", the LoadUri attribute is set to https://adb2ccustompagesdev.blob.core.windows.net/adb2c/unified.html, which means that the custom HTML page located at that URL is used. For more info.
If you're still having issues, please make sure that you have the correct LoadUri configured for all your ContentDefinition elements
Additional Links:
I hope this helps!
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
If the information helped address your question, please Accept the answer. This will help us and also improve searchability for others in the community who might be researching similar information.
Hi James,
thanks for your kind answer,
After a deeper analysis, it seem the issue about the layout is caused by the upgrade of the page layout version to 2.1.2 in order to enable the self-service password reset feature as described in this guide:
<ContentDefinition Id="api.signuporsignin">
<LoadUri>https://adb2ccustompagesdev.blob.core.windows.net/adb2c/unified.html</LoadUri>
<RecoveryUri>~/common/default_page_error.html</RecoveryUri>
<DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:2.1.2</DataUri>
<Metadata>
<Item Key="DisplayName">Signin and Signup</Item>
</Metadata>
</ContentDefinition>
Reverting back to version 1.2.0 restores the previous appearance of the page, but the embedded password feature remains non-functional. As the embedded password functionality is crucial for our application, I am reaching out to seek guidance on any additional steps that may be necessary for the configuration to work seamlessly with the version 2.1.2 page layout.
Could you please advise on any adjustments that might be required in the policies or custom pages to ensure compatibility with the new layout version? I appreciate your prompt attention to this matter, and I am available for any further clarification or information you may need.
@Sodano, Ferdinando [COMRES/COLDCHAIN/BLU]
Thank you for following up on this and I'm glad that you were able to find the cause of your issue!
When looking into the Page Layout version, I did notice that the most recent version is 2.1.17, would you be able to update your DataUri to 2.1.7 or 2.1.17 to see if that helps resolve any potential bugs with 2.1.2.
Unified sign-in and sign-up page with password reset link (unifiedssp) - Page Layout versions.
Additional Links:
I hope this helps!
If you have any other questions, please let me know. Thank you for your time and patience throughout this issue.
Hi James, the problem is not about 2.1.2 Page Layout Version specifically.
Using a newer version doesn't solve the issue.
I found a solution that works on 2.1.x Page Layout version.
Adding this snippet in ClaimsSchema solved the issue.
<ClaimType Id="signInName"> <DisplayName>Email Address</DisplayName> <DataType>string</DataType> <AdminHelpText>Email address that the user can use to sign in.</AdminHelpText> <UserHelpText>Email address to use for signing in.</UserHelpText> <UserInputType>EmailBox</UserInputType></ClaimType>
Kind regards.
@Sodano, Ferdinando [COMRES/COLDCHAIN/BLU]
I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!
If you have any other questions, please let me know. Thank you again for your time and patience throughout this issue.