Skip to content

Latest commit

 

History

History
185 lines (143 loc) · 9.19 KB

identity-provider-qq.md

File metadata and controls

185 lines (143 loc) · 9.19 KB
title description author manager ms.service ms.topic ms.date ms.author ms.subservice zone_pivot_groups
Set up sign-up and sign-in with a QQ account using Azure Active Directory B2C
Provide sign-up and sign-in to customers with QQ accounts in your applications using Azure Active Directory B2C.
garrodonnell
CelesteDG
azure-active-directory
how-to
09/16/2021
godonnell
b2c
b2c-policy-type

Set up sign-up and sign-in with a QQ account using Azure Active Directory B2C

[!INCLUDE active-directory-b2c-choose-user-flow-or-custom-policy]

::: zone pivot="b2c-user-flow"

[!INCLUDE active-directory-b2c-public-preview]

::: zone-end

Prerequisites

[!INCLUDE active-directory-b2c-customization-prerequisites]

Create a QQ application

To enable sign-in for users with a QQ account in Azure Active Directory B2C (Azure AD B2C), you need to create an application in QQ developer portal. If you don't already have a QQ account, you can sign up at https://ssl.zc.qq.com.

Register for the QQ developer program

  1. Sign in to the QQ developer portal with your QQ account credentials.
  2. After signing in, go to https://open.qq.com/reg to register yourself as a developer.
  3. Select 个人 (individual developer).
  4. Enter the required information and select 下一步 (next step).
  5. Complete the email verification process. You will need to wait a few days to be approved after registering as a developer.

Register a QQ application

  1. Go to https://connect.qq.com/index.html.
  2. Select 应用管理 (app management).
  3. Select 创建应用 (create app) and enter the required information.
  4. For the 授权回调域 (callback URL), enter https://your-tenant-name.b2clogin.com/your-tenant-name.onmicrosoft.com/oauth2/authresp. If you use a custom domain, enter https://your-domain-name/your-tenant-name.onmicrosoft.com/oauth2/authresp. Replace your-tenant-name with the name of your tenant, and your-domain-name with your custom domain.
  5. Select 创建应用 (create app).
  6. On the confirmation page, select 应用管理 (app management) to return to the app management page.
  7. Select 查看 (view) next to the app you created.
  8. Select 修改 (edit).
  9. Copy the APP ID and APP KEY. You need both of these values to add the identity provider to your tenant.

::: zone pivot="b2c-user-flow"

Configure QQ as an identity provider

  1. Sign in to the Azure portal.
  2. If you have access to multiple tenants, select the Settings icon in the top menu to switch to your Azure AD B2C tenant from the Directories + subscriptions menu.
  3. In the Azure portal, search for and select Azure AD B2C.
  4. Select Identity providers, then select QQ (Preview).
  5. Enter a Name. For example, QQ.
  6. For the Client ID, enter the APP ID of the QQ application that you created earlier.
  7. For the Client secret, enter the APP KEY that you recorded.
  8. Select Save.

Add QQ identity provider to a user flow

  1. In your Azure AD B2C tenant, select User flows.
  2. Click the user flow that you want to add the QQ identity provider.
  3. Under the Social identity providers, select QQ.
  4. Select Save.
  5. To test your policy, select Run user flow.
  6. For Application, select the web application named testapp1 that you previously registered. The Reply URL should show https://jwt.ms.
  7. Select the Run user flow button.
  8. From the sign-up or sign-in page, select QQ to sign in with QQ account.

If the sign-in process is successful, your browser is redirected to https://jwt.ms, which displays the contents of the token returned by Azure AD B2C.

::: zone-end

::: zone pivot="b2c-custom-policy"

Create a policy key

You need to store the client secret that you previously recorded in your Azure AD B2C tenant.

  1. Sign in to the Azure portal.
  2. If you have access to multiple tenants, select the Settings icon in the top menu to switch to your Azure AD B2C tenant from the Directories + subscriptions menu.
  3. Choose All services in the top-left corner of the Azure portal, and then search for and select Azure AD B2C.
  4. On the Overview page, select Identity Experience Framework.
  5. Select Policy Keys and then select Add.
  6. For Options, choose Manual.
  7. Enter a Name for the policy key. For example, QQSecret. The prefix B2C_1A_ is added automatically to the name of your key.
  8. In Secret, enter your client secret that you previously recorded.
  9. For Key usage, select Signature.
  10. Click Create.

Configure QQ as an identity provider

To enable users to sign in using a QQ account, you need to define the account as a claims provider that Azure AD B2C can communicate with through an endpoint. The endpoint provides a set of claims that are used by Azure AD B2C to verify that a specific user has authenticated.

You can define a QQ account as a claims provider by adding it to the ClaimsProviders element in the extension file of your policy.

  1. Open the TrustFrameworkExtensions.xml.

  2. Find the ClaimsProviders element. If it does not exist, add it under the root element.

  3. Add a new ClaimsProvider as follows:

    <ClaimsProvider>
  <Domain>qq.com</Domain>
  <DisplayName>QQ (Preview)</DisplayName>
  <TechnicalProfiles>
    <TechnicalProfile Id="QQ-OAuth2">
      <DisplayName>QQ</DisplayName>
      <Protocol Name="OAuth2" />
      <Metadata>
        <Item Key="ProviderName">qq</Item>
        <Item Key="authorization_endpoint">https://graph.qq.com/oauth2.0/authorize</Item>
        <Item Key="AccessTokenEndpoint">https://graph.qq.com/oauth2.0/token</Item>
        <Item Key="ClaimsEndpoint">https://graph.qq.com/oauth2.0/me</Item>
        <Item Key="scope">get_user_info</Item>
        <Item Key="HttpBinding">GET</Item>
        <Item Key="ClaimsResponseFormat">JsonP</Item>
        <Item Key="ResponseErrorCodeParamName">error</Item>
        <Item Key="external_user_identity_claim_id">openid</Item>
        <Item Key="client_id">Your QQ application ID</Item>
      </Metadata>
      <CryptographicKeys>
        <Key Id="client_secret" StorageReferenceId="B2C_1A_QQSecret" />
      </CryptographicKeys>
      <OutputClaims>
        <OutputClaim ClaimTypeReferenceId="UserId" PartnerClaimType="openid" />
        <OutputClaim ClaimTypeReferenceId="identityProvider" DefaultValue="qq.com" AlwaysUseDefaultValue="true" />
        <OutputClaim ClaimTypeReferenceId="authenticationSource" DefaultValue="socialIdpAuthentication" AlwaysUseDefaultValue="true" />
      </OutputClaims>
      <OutputClaimsTransformations>
        <OutputClaimsTransformation ReferenceId="CreateRandomUPNUserName" />
        <OutputClaimsTransformation ReferenceId="CreateUserPrincipalName" />
        <OutputClaimsTransformation ReferenceId="CreateAlternativeSecurityId" />
        <OutputClaimsTransformation ReferenceId="CreateSubjectClaimFromAlternativeSecurityId" />
      </OutputClaimsTransformations>
      <UseTechnicalProfileForSessionManagement ReferenceId="SM-SocialLogin" />
    </TechnicalProfile>
  </TechnicalProfiles>
</ClaimsProvider>

  4. Set client_id to the application ID from the application registration.

  5. Save the file.

[!INCLUDE active-directory-b2c-add-identity-provider-to-user-journey]

<OrchestrationStep Order="1" Type="CombinedSignInAndSignUp" ContentDefinitionReferenceId="api.signuporsignin">
  <ClaimsProviderSelections>
    ...
    <ClaimsProviderSelection TargetClaimsExchangeId="QQExchange" />
  </ClaimsProviderSelections>
  ...
</OrchestrationStep>

<OrchestrationStep Order="2" Type="ClaimsExchange">
  ...
  <ClaimsExchanges>
    <ClaimsExchange Id="QQExchange" TechnicalProfileReferenceId="QQ-OAuth2" />
  </ClaimsExchanges>
</OrchestrationStep>

[!INCLUDE active-directory-b2c-configure-relying-party-policy]

Test your custom policy

  1. Select your relying party policy, for example B2C_1A_signup_signin.
  2. For Application, select a web application that you previously registered. The Reply URL should show https://jwt.ms.
  3. Select the Run now button.
  4. From the sign-up or sign-in page, select QQ to sign in with QQ account.

If the sign-in process is successful, your browser is redirected to https://jwt.ms, which displays the contents of the token returned by Azure AD B2C.

::: zone-end