如何在 sign-up/sign-in 尝试时附加联合身份?
How to append federated identities at sign-up/sign-in attempt?
在 Azure AD B2C account linkage 之后,我能够成功实现 Scenario 1
和 Scenario 2
。
但是,当我尝试使用附加到第一次使用的同一电子邮件的帐户第二次联合 sign-up/sign-in 时,会创建一个新用户,而不是身份附加。
示例 account-linkage-unified 似乎是可行的方法,但根据我的理解,链接 必须是用户有意发生的。
在账户联动样本处加强:
The sample on account linkage [unified] shows you how the user can correct the problem by joining the two accounts, but that is active action by the user.
场景和预期身份
用户 foo
使用相同的 foo@email.com
Facebook、Microsoft、Google 和 Twitter 帐户;
他确实尝试使用这些帐户中的每一个来联合 sign-up/sign-in;
预期帐户:1
预期身份:
{
"displayName": "Foo Smith",
"identities": [
{
"signInType": "userPrincipalName",
"issuer": "contoso.onmicrosoft.com",
"issuerAssignedId": "foo@email.com"
},
{
"signInType": "federated",
"issuer": "facebook.com",
"issuerAssignedId": "5eecb0cd"
},
{
"signInType": "federated",
"issuer": "live.com",
"issuerAssignedId": "345678"
},
{
"signInType": "federated",
"issuer": "google.com",
"issuerAssignedId": "345678"
},
{
"signInType": "federated",
"issuer": "twitter.com",
"issuerAssignedId": "345678"
}
]
}
截至目前,Azure AD B2C Community 人员发布了解决此情况的示例策略:
在 Azure AD B2C account linkage 之后,我能够成功实现 Scenario 1
和 Scenario 2
。
但是,当我尝试使用附加到第一次使用的同一电子邮件的帐户第二次联合 sign-up/sign-in 时,会创建一个新用户,而不是身份附加。
示例 account-linkage-unified 似乎是可行的方法,但根据我的理解,链接 必须是用户有意发生的。
在账户联动样本处加强:
The sample on account linkage [unified] shows you how the user can correct the problem by joining the two accounts, but that is active action by the user.
场景和预期身份
用户 foo
使用相同的 foo@email.com
Facebook、Microsoft、Google 和 Twitter 帐户;
他确实尝试使用这些帐户中的每一个来联合 sign-up/sign-in;
预期帐户:1
预期身份:
{
"displayName": "Foo Smith",
"identities": [
{
"signInType": "userPrincipalName",
"issuer": "contoso.onmicrosoft.com",
"issuerAssignedId": "foo@email.com"
},
{
"signInType": "federated",
"issuer": "facebook.com",
"issuerAssignedId": "5eecb0cd"
},
{
"signInType": "federated",
"issuer": "live.com",
"issuerAssignedId": "345678"
},
{
"signInType": "federated",
"issuer": "google.com",
"issuerAssignedId": "345678"
},
{
"signInType": "federated",
"issuer": "twitter.com",
"issuerAssignedId": "345678"
}
]
}
截至目前,Azure AD B2C Community 人员发布了解决此情况的示例策略: