sign-up-deep-link

Sign-in and Sign-up policy with direct link to sign-up

This sample adds a direct link to the sign-up page. A relying party application can include a query string parameter option=signup that takes the user directly to the sign-up page.

To add the direct link to the sign-up page:

1. At the begging of the sign-up and sign-in user journey, add an orchestration step that reads the option claim resolver. The Get-sign-up-claim-resolver technical profile also checks the value of the option claim, and set the value of the Boolean signUpFlow claim.

   <OrchestrationStep Order="1" Type="ClaimsExchange">
     <ClaimsExchanges>
       <ClaimsExchange Id="Get-sign-up-claim-resolver" TechnicalProfileReferenceId="Get-sign-up-claim-resolver" />
     </ClaimsExchanges>
   </OrchestrationStep>

2. Then add a new orchestration step that invokes the LocalAccountSignUpWithLogonEmail sign-up technical profile. This steps runs only if the signUpFlow is True.

   <OrchestrationStep Order="2" Type="ClaimsExchange">
     <Preconditions>
       <Precondition Type="ClaimEquals" ExecuteActionsIf="true">
         <Value>signUpFlow</Value>
         <Value>False</Value>
         <Action>SkipThisOrchestrationStep</Action>
       </Precondition>
     </Preconditions>
     <ClaimsExchanges>
       <ClaimsExchange Id="SignUpExchange" TechnicalProfileReferenceId="LocalAccountSignUpWithLogonEmail" />
     </ClaimsExchanges>
   </OrchestrationStep>

3. Add a precondition to the the CombinedSignInAndSignUp orchestration step. Make is run only if the signUpFlow is False.

   <OrchestrationStep Order="3" Type="CombinedSignInAndSignUp" ContentDefinitionReferenceId="api.signuporsignin">
     <Preconditions>
       <Precondition Type="ClaimEquals" ExecuteActionsIf="true">
         <Value>signUpFlow</Value>
         <Value>True</Value>
         <Action>SkipThisOrchestrationStep</Action>
       </Precondition>
     </Preconditions>
     <ClaimsProviderSelections>
       <ClaimsProviderSelection TargetClaimsExchangeId="FacebookExchange" />
       <ClaimsProviderSelection ValidationClaimsExchangeId="LocalAccountSigninEmailExchange" />
     </ClaimsProviderSelections>
     <ClaimsExchanges>
       <ClaimsExchange Id="LocalAccountSigninEmailExchange" TechnicalProfileReferenceId="SelfAsserted-LocalAccountSignin-Email" />
     </ClaimsExchanges>
   </OrchestrationStep>

Set the authorization request

To direct the user to the sign-up page, in the authorization request add the option=signup query string parameter.

The following example takes the user to the landing page (sign-up or sign-in)

https://yourtenant.b2clogin.com/yourtenant.onmicrosoft.com/oauth2/v2.0/authorize?p=B2C_1A_signup_signin_with_link_to_sign_up&client_id=63ba0d17-c4ba-47fd-89e9-31b3c2734339&nonce=defaultNonce&redirect_uri=https%3A%2F%2Fjwt.ms&scope=openid&response_type=id_token

If you add the option=signup parameter, the user is taken directly to the sign-up page.

https://yourtenant.b2clogin.com/yourtenant.onmicrosoft.com/oauth2/v2.0/authorize?p=B2C_1A_signup_signin_with_link_to_sign_up&client_id=63ba0d17-c4ba-47fd-89e9-31b3c2734339&nonce=defaultNonce&redirect_uri=https%3A%2F%2Fjwt.ms&scope=openid&response_type=id_token&option=signup`

Community Help and Support

Use Stack Overflow to get support from the community. Ask your questions on Stack Overflow first and browse existing issues to see if someone has asked your question before. Make sure that your questions or comments are tagged with [azure-ad-b2c]. If you find a bug in the sample, please raise the issue on GitHub Issues. To provide product feedback, visit the Azure Active Directory B2C Feedback page.

Notes

This sample policy is based on SocialAndLocalAccounts starter pack. All changes are marked with Sample: comment inside the policy XML files. Make the necessary changes in the Sample action required sections.