question

HarjaniAshish-7896 avatar image
0 Votes"
HarjaniAshish-7896 asked JamesTran-MSFT commented

Azure B2C - Custom User Flow for Phone Sign Up - Not persisiting Extension attributes

Hi,

I am trying to embed the Terms of Consent page in the Phone Sign Up Custom User Flows, everything is working fine except that the Terms of Consent Page comes up always even if the user already agreed to it. I implemented this in Email Sign Up Custom User Flow and things work exactly as expected there, but having trouble with Phone Sign Up Flows.

Blog I am referring to implement this : https://justidm.wordpress.com/2018/10/01/add-a-terms-of-use-consent-page-to-azure-ad-b2c-user-journey-with-custom-policies/

Above blog refers to implement in EmailSignUP Custom User Flow , and it works fine for me there, but I tried same concept in Phone Sign Up Custom User Flow but it seems that ReadUserWithObjectID step is not working the way it should. Ideally it should persist the TermsofConsent extension attribute once and next time user signs in should match the criteria and NOT bring up that page again. But in my case, it always brings up consent page no matter if user already agreed to that at the first time.

Downloaded Phone Sign Up Custom User Flow from : https://github.com/Azure-Samples/active-directory-b2c-custom-policy-starterpack/tree/master/scenarios/phone-number-passwordless

83730-image.png


azure-ad-b2c
image.png (24.9 KiB)
5 |1600 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.

1 Answer

HarjaniAshish-7896 avatar image
1 Vote"
HarjaniAshish-7896 answered JamesTran-MSFT commented

I figured out the issue for this. It seems by default the Phone Sign UP Base Policy - Read User By Object ID orchestration step is skipped every time since it already has all the default claims unlike in Email Sign Up User Flows where they are always executed. So I made a change in Phone Sign Up Custom User Flow to always execute that step and now it is able to get the extension attributes from B2C and do the needful. This is just for anyone who might be stuck on similar issue.

· 1
5 |1600 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.

@HarjaniAshish-7896
Thank you for following up on this and I'm glad that you were able to resolve your issue!


Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.

0 Votes 0 ·