Skip to main content

Amazon

note

To add Amazon as a social sign-in provider, you need a Amazon Developer account. Go to Amazon Developers to create one.

Follow these steps to add Amazon as a social sign-in provider for your project, using the Ory Console.

  1. Go to AuthenticationSocial Sign-In in the Ory Console.
  2. Enable the Enable OpenID Connect toggle, then click Add new OpenID Connect provider.
  3. Click the Amazon logo to open the Configure Amazon screen. You may need to click Show more providers to see the full list of providers.
  4. Copy the Redirect URI and save it for later use.
  5. Follow the official steps to create a security profile.
  6. Copy the Client ID and Client secret from Amazon and paste them into the corresponding fields in the Ory Console.
  7. On Amazon Developers, click Save Changes.
  8. On Amazon Developers, go to Settings > Security Profiles > [Your profile] > Web Settings .
  9. Paste the redirect URI copied from Ory into the Allowed Returned URLs and click Save Changes.
  10. In the Ory Console, click Save Configuration to enable Amazon as a social sign-in provider.
note

These steps cover the basic configuration of a social sign-in provider integration. At this point, the user experience is incomplete. To complete the configuration and ensure a smooth and secure user experience, configure the scopes and data mapping as described in the next section.

Additional configuration

When adding a social sign-in provider, you can customize the integration by defining the OAuth scopes Ory requests from the provider and by setting up custom data mappings.

Scopes

The Scopes section allows you to define the OAuth scopes Ory requests from the sign-in provider. Defining scopes allows you to interact with the provider's APIs on behalf of the user, or to access additional user data, which is exposed as claims for data mapping.

For Amazon, add the profile scope for a basic setup.

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

Data mapping

In the Data mapping field, you can map the data returned by the sign-in provider to traits as defined in the identity schema.

To define the mapping, create a Jsonnet code snippet. Read this document to learn more about Jsonnet data mapping.

In this sample Jsonnet snippet, the user's email, is mapped to email in the identity schema.

local claims = std.extVar('claims');
{
identity: {
traits: {
// The email might be empty if the user hasn't granted permissions for the email scope.
[if 'email' in claims then 'email' else null]: claims.email,
},
},
}

Troubleshooting

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.