Clone access tokens

Cloning of access tokens enables CONNECT services to extend the validity of the access tokens automatically.

Currently, access tokens are cloned using the CONNECT SDK. The SDK accepts requests for cloning access tokens and create a new access token from an original token. The request must contain the Id of the original token along with the new expiry date.

Cloning creates a new access token. After successfully cloning, the new (cloned) access token is displayed on Integrations > Access tokens page. For such tokens, the Cloned From column displays the name of the original access token. The name of the cloned token is same as the original token, but is appended by (X) where X represents the number of times the original access token was cloned. After cloning, the original access token is not affected, except a reference is added to point to the new clone.

An access token can be cloned any number of times. Also, a clone of a clone can be created. For example, you have created an access token by name token that expires in a week. Before the expiry, a clone of token can be created that takes the name token (1), and extend its validity by one more week. Later, a clone of token (1) can be created that takes the name token (2), and extend it by one more week and so on. This way, the validity of an access token can be extended as required, and the end-applications can run without interruptions.

If you delete an original access token, the access tokens cloned from it continue to remain active.

You can view the clone history of an access token by selecting the vertical ellipsis corresponding to the access token on the Access tokens page and selecting Clone history.

Currently, this capability is available only through service to service calls. Contact your AVEVA representative for more information about cloning access tokens.