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:
This call requires Basic Authorization. To create the authorization code for this call, your
configuration_client_secret must be combined with a colon in between (id:secret) and then base64 encoded.
You can find the Configuration Client ID and Secret in the Identity Cloud Console:
configuration_client_secretsettings under Global Settings in the Custom Settings section
What if I don’t have these settings? You may not have these settings if your original implementation of Identity Cloud predates Hosted Login. If you do not know your configuration client ID and secret, and do not know how to find them, please reach out to your Akamai Identity Cloud representative and we’ll be happy to help.
Postman will create the authorization code for you. All you need to do is:
configuration_client_idas the Username and your
configuration_client_secretas the Password
When you Send the call, Postman will generate the Authorization header for you, and this will override the Authorization template from the imported call.
curl -X POST \ https://v1.api.REGION.janrain.com/CUSTOMER_ID/login/token \ -H 'Authorization: Basic AUTHORIZATION CODE' \ -H 'Content-Type: application/x-www-form-urlencoded' \ -d 'grant_type=client_credentials' \ -d 'scope=*:config/**'
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.
access_token from your call’s response below. We’ll use this in the next step.
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.