Connector Exception 8: Invalid Thing token property
This exception appears if a Thing that was communicating for a long time but no longer appears to be communicating. A symptom could be that its lastConnected property is not updating or that expected data item messages are not showing up. Note that if a Thing name is null, token authentication always fails. For more information, refer to Observation 2: The lastConnection property of the Thing does not update and Observation 3: Asset was communicating earlier, but now it does not communicate.
The following scenario would result in this exception:
1. Start ThingWorx Platform.
2. Start eMessage Connector
3. Create a Thing on the ThingWorx Platform, using the AxedaStandaloneModel Thing Template and set the token property to bogus.
4. Start an Axeda Connector agent that is configured to send data item messages to the Connector.
* 
This scenario would be the same for an asset that is running the Axeda Gateway agent and has a corresponding Things in the ThingWorx Platform (created using the AxedaEmessageGatewayModel Thing Template).
In this scenario, the Connector attempts to authenticate the token sent by the agent against the token stored in the Thing token property. This authentication fails. No eMessages are processed, and the warning message that is logged includes the following information::
...[vert.x-worker-thread-3]
WARN c.t.p.e.c.TokenAuthenticationConverter -
Token authentication failure detected or Thing=Weather1
modelNumber=WeatherModel serialNumber=Weather1
failureMessage=Authentication failed:
Unable to dispatch [ uri = ...:
Unable to Invoke Service ValidateToken on
TokenPropertyAuthenticator : Tokens do not match.
For information about the token property, configuration of the TokenPropertyAuthenticator, behavior of the TokenPropertyAuthenticator, and resetting a token, refer to the following topics:
Security and the eMessage Connector (the subsection on token authentication)
Was this helpful?