You can activate a selected version of the key collection on the staging network, and then, after testing and validating it, you can activate this version on the production network.

Each activation process may take up to 30 minutes and you can track progress of the activation in the key collection's details view.

You can activate only one version at a time on the staging or production network. By activating a version, you deactivate the previous one.

Activate a key collection on staging

The staging network lets you test your public keys without impact to production configurations. After testing the functionality, you can use the same key collection in production.

1. In Token Access Control Access, click Manage next to the appropriate key collection name.

2. On the key collection name page, click the version that you want to activate in staging.

   The system numbers key collection versions in ascending order with the highest number indicating the latest version.

3. On the version page, click Activate on staging.

Activate a key collection on production

By activating a key collection version on production, you rotate public keys used by your property to verify JWT signatures in client requests. By default, property-referenced key collections use public keys indicated in their active versions.

1. In JWT Access Control Access, click Manage next to the appropriate key collection name.

2. On the key collection name page, click the version that you want to activate in production.

   The system numbers key collection versions in ascending order with the highest number indicating the latest version.

3. On the page, click Activate on production.

Next steps after each activation

Once you've activated the key collection version on the staging or on the production network, you can select it in the JWT behavior of the property that you want to use it the production network. See Configure the JWT behavior for IoT OTA Updates.