Add Spotify as a social sign-in provider in Ory
Configuration for The Ory Network
Follow these steps to add Spotify as a social sign-in provider to your project using the Ory CLI:
In the created app, set the redirect URI to:
https://<ory-project-slug>.projects.oryapis.com/self-service/methods/oidc/callback/spotify
Create a Jsonnet code snippet to map the desired claims to the Ory Identity schema.
local claims = std.extVar('claims');
{
identity: {
traits: {
email: claims.email,
},
},
}infoSpotify provides an OIDC discovery URL, but it doesn't support the
openid
claim and returns theaccess_token
only. Ory sends requests to Spotify's /me API and adds the user info tostd.extVar('claims')
.
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 The Ory Network.
Encode the Jsonnet snippet with Base64 or host it under an URL accessible to The Ory Network.
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
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.
selfservice:
methods:
oidc:
config:
providers:
- id: spotify # this is `<provider-id>` in the Authorization callback URL. DO NOT CHANGE IT ONCE SET!
provider: spotify
client_id: .... # Replace this with the OAuth2 Client ID provided by Spotify
client_secret: .... # Replace this with the OAuth2 Client Secret provided by Spotify
mapper_url: "base64://<YOUR_BASE64_ENCODED_JSONNET_HERE>"
# Alternatively, use an URL:
# mapper_url: https://storage.googleapis.com/abc-cde-prd/9cac9717f007808bf17f22ce7f4295c739604b183f05ac4afb4
scope:
- user-read-email
- user-read-private
enabled: trueUpdate the Ory Identities (Ory Kratos) configuration using the file you worked with:
ory update identity-config <project-id> --file updated_config.yaml
Configuration for self-hosted instances
Follow these steps to add Spotify as a social sign-in provider when self-hosting Ory Kratos:
Set the redirect URI to URL that follows this pattern:
http(s)://<domain-of-ory-kratos>:<public-port>/self-service/methods/oidc/callback/spotify
Create a Jsonnet code snippet to map the desired claims to the Ory Identity schema.
Encode the Jsonnet snippet with Base64 or store it in a location available to your Ory Kratos instance.
Add the social sign-in provider configuration to the Ory Kratos configuration. Add the Jsonnet snippet with mappings as a Base64 string or provide a path or an URL of the file.
When running a self-hosted instance, you can pass the social sign-in provider configuration in the
SELFSERVICE_METHODS_OIDC_CONFIG_PROVIDERS
environment variable. For example:
SELFSERVICE_METHODS_OIDC_CONFIG_PROVIDERS='[{"id":"google","provider":"google","mapper_url":"<file_location>","client_id":"<client_id>","client_secret":"<client_secret>","scope":["openid","email","profile"],"auth_url":"https://accounts.google.com/o/oauth2/v2/auth","token_url":"https://www.googleapis.com/oauth2/v4/token","issuer_url":"https://accounts.google.com"}]'
Prevent having to log in after sign-up
When adding social sign-in providers manually, remember to add the session
hook to after/oidc/hooks
. If you don't add this
hook, users will have to log in again after signing up to get a session.
selfservice:
flows:
registration:
after:
oidc:
hooks:
- hook: session