Can we have two sets of Azure B2C sign-in custom policies for the application?

Karikalan Ramakrishn 236 Reputation points
2021-08-13T13:19:46.523+00:00

I have a requirement to project different type of B2C sign-in page to end user? For example, User type-1: will be using the user name or email-id to sign-in with self service password reset option. (B2C_1A_SIGNUP_SIGNIN - File 1)

User type-2: Will be signing in only by using the user name and no Forgot password link and self service password reset option provided. (B2C_1A_SIGNUP_SIGNIN - File 2)

Based on my understanding, I will have to create two different custom policy for user type 1 & 2? Is that right? If yes, how about B2C_1A_TRUSTFRAMEWORKBASE and B2C_1A_TRUSTFRAMEWORKEXTENSIONS files - do I need to have seperate copy of these w.r.t user type please? Thanks.

Microsoft Entra External ID
Microsoft Entra External ID
A modern identity solution for securing access to customer, citizen and partner-facing apps and services. It is the converged platform of Azure AD External Identities B2B and B2C. Replaces Azure Active Directory External Identities.
2,892 questions
0 comments No comments
{count} votes

Accepted answer
  1. AmanpreetSingh-MSFT 56,626 Reputation points
    2021-08-16T08:00:15.463+00:00

    Hi @Karikalan Ramakrishn • Thank you for reaching out.

    Yes, you will have to create two set of policy files. You can choose to create two separate chains, as mentioned below:

    • B2C_1A_TRUSTFRAMEWORKBASE > B2C_1A_TRUSTFRAMEWORKEXTENSIONS > B2C_1A_SIGNUP_SIGNIN
    • B2C_1A_TRUSTFRAMEWORKBASE1 > B2C_1A_TRUSTFRAMEWORKEXTENSIONS1 > B2C_1A_SIGNUP_SIGNIN1

    However, it is not necessary to use 2 set of policy files, if you want to use 2 RP (B2C_1A_SIGNUP_SIGNIN) files. You may also consider creating 2 separate user journeys in your B2C_1A_TRUSTFRAMEWORKBASE or B2C_1A_TRUSTFRAMEWORKEXTENSIONS file, e.g., <UserJourney Id="SignUpOrSignIn"> and <UserJourney Id="SignUpOrSignIn1">.

    Once you have the two User Journeys configured, in B2C_1A_SIGNUP_SIGNIN file you can reference <DefaultUserJourney ReferenceId="SignUpOrSignIn" /> and in B2C_1A_SIGNUP_SIGNIN1 file, reference <DefaultUserJourney ReferenceId="SignUpOrSignIn1" />

    If you use this configuration, the policy file chains will look like:

    • B2C_1A_TRUSTFRAMEWORKBASE > B2C_1A_TRUSTFRAMEWORKEXTENSIONS > B2C_1A_SIGNUP_SIGNIN
    • B2C_1A_TRUSTFRAMEWORKBASE > B2C_1A_TRUSTFRAMEWORKEXTENSIONS > B2C_1A_SIGNUP_SIGNIN1

    -----------------------------------------------------------------------------------------------------------

    Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

    1 person found this answer helpful.

0 additional answers

Sort by: Most helpful

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.