The Axeda® Platform uses tokens to identify assets that should be allowed to communicate with the Platform. Each Agent generates its own token and includes it in the registration message with the Platform and then in each subsequent communication to the Platform. Tokens are saved in an encrypted format. If an Agent sends an invalid token or no token, the Platform ignores the message and then locks out that asset for a period of 10 minutes. If a Gateway Agent registers with a unique token, but one of its managed assets registers with an invalid token, the Platform ignores messages from that managed asset but accepts and processes messages from the Gateway and all other assets managed by the Gateway. The managed asset with the invalid token is locked out for 10 minutes.
The Platform considers a token invalid if:
o The token is not unique.
o The asset sends a message using a token that differs from the token sent with the registration message that the asset sent originally.
o The token is missing from a message.
In each of these cases, the Platform ignores the message and locks the asset out for 10 minutes.
To reset a token at the asset, locate and remove the AssetUUIDs.dat file. Then, shut down and restart the Agent. When it starts, the Agent determines that the AssetUUIDs.dat file is missing and recreates the token. From the View and manage assets page, another user must reset the token for the asset to ensure that communications are re-established between the asset and the Platform.