question

Octopus-1 avatar image
0 Votes"
Octopus-1 asked ·

Layout version upgrade in custom policy Azure B2C not always working

Hi,
I know that this sort of question has been asked before, but there seems to be a strange behavior and I would like to know if this is a known issue or if I am missing something:
I am testing out IEF instead of the built in userflows in Azure B2C and since we need utf-8 languages, I need to use version 2.1.2.
Following the instructions I added a content definition which has for signupsignin

<DataUri>urn:com:microsoft:aad:b2c:elements:contract:unifiedssp:1.0.0</DataUri>

and upgraded it to a higher version. Version 1.2.0 seems to work as the UI shows the id of the email field as "email" instead of "signinName", but when I upgrade to 2.1.2 it falls back to signInName. But 2.1.2 should show an id of email as per the built-in userflow.
If I use an inexisting version, e.g. 2..2.9, then the portal complains and lists all version up to 2.1.2.

I have two questions:
1) Is that expected as a bug or should I add more to the content definition for the signupsignin page?
2) How do I know which version the Azure B2C server is flushing in my browser? For now I am using hints such as the change in id name in the input field, but that is very limited.

Thank you for your help








azure-ad-b2c
· 1
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thanks @Octopus.
1. This is is a known issue with the page layout versions (2.1.0 and 2.1.1) and is already reported to the product team. Please try using page layout version 2.1.2.

If you still face this issue, as a workaround you can use page layout version 1.2.0 or lower version.

If you are using User Flow, you can use Standard User flow which supports layout version 1.2.0 and lower versions.

Read More about page layout versions: https://docs.microsoft.com/en-us/azure/active-directory-b2c/page-layout

1 Vote 1 ·
SvenGloeckner avatar image
0 Votes"
SvenGloeckner answered ·

@JitendraRai-2073
Thanks for clarification. I came to the same problem.

However the following is working in my environment:

 <LocalizedString ElementType="ClaimType" ElementId="signInName" StringId="DisplayName">Please enter your email</LocalizedString>

Be sure to empty your browser cache. I had some trouble with old settings due to browser caching.

There seems to be another issue as well.
In the doc we read:

Added a UXString heading in addition to intro to display on the page as a title. This is hidden by default.

However, this heading is never rendered in html. It's even not hidden.


·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SaloniDaga-5145 avatar image
0 Votes"
SaloniDaga-5145 answered ·

@JitendraRai-2073 : We are using userflows and it supports only layout version 1.2.0 and below.

We have a accessibility bug that the heading "Sign in with the social account" is annouced as h2 instead of h1.

Looks like version 2.1.x might fix this issue as it provides the UXString heading. Is there any plan to fix the existing issue with SvenGLoeckner reported above. As we dont plan to migrate to custom flow. Is there any option to upgrade the user flows , page layout version to >1.2.0?

" Added a UXString heading in addition to intro to display on the page as a title. This is hidden by default."

· 1 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.