An endpoint join token is a special-purpose, system-generated alphanumeric string used to authenticate endpoint, which can then automatically associate itself with its user account and establish a connection to the BloxOne services.
Create as many join tokens as you need, and use them for different purposes, such as the following:
Use the same join token to deploy multiple endpoints.
Create a join token to provision endpoint, and assign it to your Cloud Services Portal account.
Create a short-lived join token for an admin who wants to join endpoints. When the admin finishes the task, revoke the join token and thus prevent the admin from provisioning new endpoints.
Revoke a join token if it has been compromised, to prevent its use in provisioning of new endpoints. Note that join tokens are valid until you revoke them through the Cloud Services Portal or expire.
The Manage > Endpoints > Join Tokens page displays the following information for each join token you have created:
TOKEN NAME: The token’s name.
STATUS: The token’s current status: Enabled or Disabled.
COUNT: The number of times you have used the token to set up your endpoints.
This number is useful for security purposes. For example, if you have used a join token to connect a certain number of endpoints, and if that number does not match the value of COUNT, then you might want to review the endpoints that have joined your network.
LAST USED: The timestamp of the token’s last use, formatted as mm/dd/yy hh:mm:ss time zone.
DESCRIPTION: Information about the join token.
ENDPOINT GROUP: The endpoint group assignment for the join token.
EXPIRATION DATE: The join token’s date of expiry. The join token will no longer function past this date.
For more information about endpoint join tokens, see the following:
For information on BloxOne Mobile Endpoint, see Managing Mobile Endpoint.