Azure-Samples / Azure-Samples/active-directory-b2c-custom-policy-starterpack

How do I integrate multiple signin policies on one page?

Open
#116 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
360
Forks
398
PR merge metrics
No merged PRs in 30d

Description

Hello,

How do I integrate multiple signin policies on one page?
SignIn policies :
1、Phone + password
2、Phone + verificationCode
3、WeChat

I tried to integrate the above three strategies into one UserJourney. Here is my policy

```xml

















objectId
SkipThisOrchestrationStep












authenticationSource
localAccountAuthentication
SkipThisOrchestrationStep










objectId
SkipThisOrchestrationStep










authenticationSource
socialIdpAuthentication
SkipThisOrchestrationStep














PolicyProfile














Local Account Sign Up With Phone



VerificationCode


IpAddress
api.selfasserted
continue


























wechat.com
WeChat (Preview)


WeChat


wechat
https://open.weixin.qq.com/connect/qrconnect
https://api.weixin.qq.com/sns/oauth2/access_token
https://api.weixin.qq.com/sns/userinfo
snsapi_login
GET
json
appid
secret
openid
openid
errcode
unionid
wxxxxxxxxxxxxxxxxxx

































```

The phone number + password can be used to successfully signin and obtain the token.
But, the mobile phone number and verification code cannot signin and obtain the token. After passing the verification code, the user does not sign in directly and redirect to changes the mobile phone number.
And, after the wechat login is scanned successfully using the mobile phone and the login is confirmed in wechat, the page for resetting the password is redirected instead of directly logging in to obtain the token.

Could you give me some guidance?
Many thanks.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reviewing the XML UserJourney, especially orchestration step 2 and the LocalAccountSignInWithPhoneCode technical profile. Trace the phone verification flow after validation and compare it with the phone-and-password path. Done means the verification-code policy completes sign-in, returns the expected token, and does not redirect to change the phone number.

Written by the indexing model from the issue text.

Assessment

Tech stack
azure
Domain
authentication
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.