Skip to main content


Follow these steps to add DingTalk as a social sign-in provider to your project using the Ory CLI:

  1. Create a DingTalk OAuth app.

  2. In the created app, set the redirect URI to:

  3. Create a Jsonnet code snippet to map the desired claims to the Ory Identity schema. Specific information DingTalk's User API can be viewed.

    local claims = std.extVar('claims');
    identity: {
    traits: {
    // Allowing unverified email addresses enables account
    // enumeration attacks, especially if the value is used for
    // e.g. verification or as a password login identifier.
    // Therefore we only return the email if it (a) exists by DingTalk.
    [if "email" in claims then "email" else null]:,

Don't save secrets such as API keys, credentials, or personal data directly in Jsonnet code snippets. Jsonnet code snippets used for data mapping aren't stored in an encrypted format in Ory Network.

  1. Encode the Jsonnet snippet with Base64 or host it under an URL accessible to Ory Network.

    cat your-data-mapping.jsonnet | base64
  2. Download the Ory Identities config from your project and save it to a file:

    ## List all available projects
    ory list projects

    ## Get config
    ory get identity-config {project-id} --format yaml > identity-config.yaml
  3. Add the social sign-in provider configuration to the downloaded config. Add the Jsonnet snippet with mappings as a Base64 string or provide an URL to the file.

    enabled: true
    - id: dingtalk # this is `<provider-id>` in the Authorization callback URL. DO NOT CHANGE IT ONCE SET!
    provider: dingtalk
    client_id: .... # Replace this with the OAuth2 Client ID provided by DingTalk
    client_secret: .... # Replace this with the OAuth2 Client Secret provided by DingTalk
    mapper_url: "base64://{YOUR_BASE64_ENCODED_JSONNET_HERE}"
    # Alternatively, use an URL:
    # mapper_url:
    # DingTalk supports only the `openid` or `openid corpid` scopes. For a basic setup, use the `openid` scope.
    - openid

    To learn more about the scopes available for DingTalk, read the related documentation.

  4. Update the Ory Identities configuration using the file you worked with:

    ory update identity-config {project-id} --file identity-config.yaml


When you add a social sign-in provider, you can encounter common problems such as:

  • Redirect URI mismatch
  • Redirect loops during registration
  • Domain verification issues

To troubleshoot those issues, read Social sign-in troubleshooting.