Upgrade OIDC client

Now that you’ve created a v2 login policy, you can use it to upgrade your OIDC client(s) to Hosted Login v2.

We’ll continue to use the same access token you provisioned earlier. This token lasts one hour - if it expires, you can go back and provision a new one.

Step 1: GET OIDC client configuration

Call the /config/clients/<janrainOidcClientId> endpoint with GET method to get your OIDC client configuration again. As you observed previously, this configuration includes your loginPolicy identifier.

curl -X GET \
https://v1.api.REGION.janrain.com/CUSTOMER_ID/config/clients/OIDC_CLIENT_ID \
	-H 'Authorization: Bearer ACCESS_TOKEN'

Step 2: Edit client configuration

Copy the full JSON object from the response and paste it into the text area below.

Then make the following change:

  • Update the loginPolicy value to point to your new v2 login policy: If you don’t see a login policy ID here, go back and complete the previous steps.
See example of an updated client configuration

Tip! The _links property is not configurable and can be safely removed from the JSON for simplicity, as in the example above.

Step 3: PUT client configuration

To publish your client configuration with the v2 loginPolicy, call the same endpoint with the PUT method, passing the full, updated JSON object in the body of the call.

curl -X PUT \
https://v1.api.REGION.janrain.com/CUSTOMER_ID/config/clients/OIDC_CLIENT_ID \
	-H 'Authorization: Bearer ACCESS_TOKEN' \
	-H 'Content-Type: application/json' \
Troubleshooting Tips

Upon success, your client is now upgraded to Hosted Login v2! You can test the digital property associated with this OIDC client to see the new v2 features.

NOTE: In order to use Hosted Login v2, you only need to update the loginPolicy. It is NOT necessary to update your Hosted Login calls (such as the /auth-ui/profile endpoint) to also refer to v2. When your loginPolicy is upgraded to v2, that becomes the default version for all Hosted Login calls you make with the associated OIDC client.