Howdy, folks!
I’m excited to announce that customizing your user flows with Azure AD B2C is now easier than ever with more features, including the general availability of our new portal experie...
Great post! Glad to see that we can finally customize the page UI for the Sign In V2 flow.
One thing we did notice is that in the Sign In V2 flow, it has inherited some behaviors from the SignInOrSignUp policy. Namely, if you create a user via the Azure Graph API and force them to change password in initial log in, the SignInOrSignUp policy does not recognize the user. Whereas the previous SignIn V1 flow, would recognize the user, go to the change password prompt page, then redirect to the appropriate application target.
What would be nice is if the SignInV2 would behave the same as SignInV1, i.e. go to the change password prompt page the first time a new user signs in.
Attached is a screenshot of the API call we're using.
Noticable difference between signinv1 (red) and signinv2 (green)example payloadexample of what happens if we try to sign in using signinv2example of what happens if we try the same credentials on a signinv1 flow