Page tree
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Experimental

Service Tokens are an experimental feature, and may be significantly changed or even removed completely in a future release. 

Service Tokens are currently implemented as an optional plugin, and must be enabled. Once enabled, Service Tokens will be available for all COs on the platform that have CO Services defined.

Background

CO Service Tokens are an implementation of application specific passwords.

Configuration

 

Restrictions

There are various restrictions with the current implementation:

  1. Only plaintext tokens of 8 or 15 characters are supported.
  2. Once set, a token cannot be revoked completely, though it can be changed.
  3. Although provisioning is initiated when a Service Token is set, provisioners do not currently have access to the Service Token records via the normal mechanism for accessing provisioning data. In other words, there is no out of the box mechanism for accessing Service Tokens. A custom provisioner must be written.
  4. Although administrators can technically assign tokens on behalf of a user, there is no link from the CO Person canvas page to do so.

 

See Also

  • No labels