Get configuration token

In order to configure your login policy(ies), you must first obtain an access token to authorize your configuration. To do this, you’ll make a call to the Hosted Login configuration endpoint: /login/token

This call requires Basic Authorization. To create the authorization code for this call, your configuration_client_id and configuration_client_secret must be combined with a colon in between (id:secret) and then base64 encoded.

Find my configuration client id and secret
How to create the authorization code in Postman
curl -X POST \ \
	-H 'Authorization: Basic AUTHORIZATION CODE' \
	-H 'Content-Type: application/x-www-form-urlencoded' \
	-d 'grant_type=client_credentials' \
	-d 'scope=*:config/**'

The scope in this case will grant your token full read/write access to all Hosted Login configuration endpoints. Note that this scope must match a scope defined in your configuration client. If you’ve defined different scopes for your configuration client, you may need to use a different scope here.

Enter the access_token from your call’s response below. We’ll use this in the next step.

See example of an access token

The next steps will guide you through the generally recommended approach for upgrading to Hosted Login v2 - creating a new v2 login policy that works concurrently with your existing v1 login policy(ies). This allows you to upgrade your digital properties to v2 one at a time.

If you prefer a more direct approach, you can upgrade your existing login policy directly, which will have an immediate impact on all clients associated with it. See the Alternate Approach.