The following table describes the Trusted Access client properties. All of this information is encrypted when it is stored in the Composer metadata store, except the client secret, which is hashed using BCrypt.
|The human-readable string name of the client application. The client name must be unique.|
|The client ID issued to the client when the client is registered with Trusted Access. This is generated by the system and cannot be modified.|
|The client secret string issued to the client when the client is registered with Trusted Access. This value is used by applications to authenticate to the token endpoint. The client secret is not available after it is initially created -- developers must store it locally in order to retain it.|
|The validity (in seconds) of the access token. Short-lived tokens (less than 10 minutes) are recommended.|
|The time (in seconds) at which the |
|A string indicator of the authentication method used for the token endpoint. For Trusted Access, this value is always |