Tokens for secure authentication of targets

Two types of token are used as part of the implementation for secure target registration in Remote Control.

The secure target registration property must also be enabled. For more information, see Secure target registration.

The tokens are generated by the Remote Control server.
Registration token
A token that is used to authenticate a target when it initially contacts the server. The token is used for new target registrations and also when you reinstall a target whose details are still in the database. You can create a token in the server UI and specify a validity period for the token. For more information about creating a registration token, see Creating a secure registration token.
Endpoint token
A token that is sent to a target after it registers with the server. The target stores the token and uses it for all subsequent callhomes to the server. The token is also saved in the target details in the database. To allow the target details to be updated, the token in the database must match the token that is stored on the target. The Endpoint token is valid until the target entry is deleted from the database. For more information about how the tokens are used to authenticate the targets, see How targets securely authenticate with the server.

The target includes the token in its callhome to the server only when it uses a secure connection to the server. The server URL that it uses to connect to the server must start with HTTPS.