-
Suggestion
-
Resolution: Fixed
-
None
-
1
-
Issue Summary
Starting 7.0.3 Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent.
An error "Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified." is thrown at the discovery tool as Discovery agent sends a unique token to discovery tool and reinstallation creates a mismatch. This scenario can be solved by regenerating discovery token (Which needs to be replaced on all the running agents)
A feature to revoke the token for a specific agent will be handy for customers with large number of agents installed.
Workaround (Any one of the below options )
- Create a new token on discovery and update them on agents
- Issue is not observed on 7.0.1
- When uninstalling agent, don't delete the agent installation directory.
- mentioned in
-
Page Failed to load
[JSDSERVER-15438] Revoke token for a specific agent
| Fix Version/s | New: Discovery 7.0.5 [ 109395 ] | |
| Resolution | New: Fixed [ 1 ] | |
| Status | Original: Gathering Interest [ 11772 ] | New: Closed [ 6 ] |
| Remote Link | New: This issue links to "Page (Confluence)" [ 936484 ] |
| Description |
Original:
h3. Issue Summary
Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent This is reproducible on Data Center: Yes h3. Steps to Reproduce # Install Discovery agent # Update the token for the agent by copying token from discovery tool # Uninstall the agent and reinstall on the same machine # Configure the agent with the same token from Assets discovery h3. Expected Results # Agent should be identified by Discovery tool and status updated correctly. h3. Actual Results # Agent is identified by the Discovery tool, withe the message "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified." # The agent is unable to connect and transfer data to discovery. The below exception is thrown in the Discovery log file: {code:java} Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified. {code} The below exception is thrown in the Discovery log file: {code:java} [Error] Failed to decrypt credentials {code} !screenshot-1.png|thumbnail! h3. Workaround (Any one of the below options ) * Create a new token on discovery and update them on agents * Issue is not observed on 7.0.1 * When uninstalling agent, don't delete the agent installation directory. |
New:
h3. Issue Summary
Starting 7.0.3 Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent. An error "Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified." is thrown at the discovery tool as Discovery agent sends a unique token to discovery tool and reinstallation creates a mismatch. This scenario can be solved by regenerating discovery token (Which needs to be replaced on all the running agents) A feature to revoke the token for a specific agent will be handy for customers with large number of agents installed. h3. Workaround (Any one of the below options ) * Create a new token on discovery and update them on agents * Issue is not observed on 7.0.1 * When uninstalling agent, don't delete the agent installation directory. |
| Summary | Original: Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent | New: Revoke token for a specific agent |
| Affects Version/s | Original: Discovery 7.0.4 [ 107811 ] | |
| Affects Version/s | Original: Discovery 7.0.3 [ 107796 ] | |
| Workflow | Original: JAC Bug Workflow v3 [ 4475338 ] | New: JAC Suggestion Workflow 3 [ 4475747 ] |
| Issue Type | Original: Bug [ 1 ] | New: Suggestion [ 10000 ] |
| Priority | Original: Low [ 4 ] | |
| Status | Original: Needs Triage [ 10030 ] | New: Gathering Interest [ 11772 ] |
| Support reference count | New: 1 |
| Description |
Original:
h3. Issue Summary
Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent This is reproducible on Data Center: Yes h3. Steps to Reproduce # Install Discovery agent # Update the token for the agent by copying token from discovery tool # Uninstall the agent and reinstall on the same machine # Configure the agent with the same token from Assets discovery h3. Expected Results # Agent should be identified by Discovery tool and status updated correctly. h3. Actual Results # Agent is identified by the Discovery tool, withe the message "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified." # The agent is unable to connect and transfer data to discovery. The below exception is thrown in the Discovery log file: {code:java} Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified. {code} The below exception is thrown in the Discovery log file: {code:java} [Error] Failed to decrypt credentials {code} !screenshot-1.png|thumbnail! h3. Workaround * Create a new token on discovery and update them on agents * Or, downgrade to 7.0.1 |
New:
h3. Issue Summary
Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent This is reproducible on Data Center: Yes h3. Steps to Reproduce # Install Discovery agent # Update the token for the agent by copying token from discovery tool # Uninstall the agent and reinstall on the same machine # Configure the agent with the same token from Assets discovery h3. Expected Results # Agent should be identified by Discovery tool and status updated correctly. h3. Actual Results # Agent is identified by the Discovery tool, withe the message "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified." # The agent is unable to connect and transfer data to discovery. The below exception is thrown in the Discovery log file: {code:java} Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified. {code} The below exception is thrown in the Discovery log file: {code:java} [Error] Failed to decrypt credentials {code} !screenshot-1.png|thumbnail! h3. Workaround (Any one of the below options ) * Create a new token on discovery and update them on agents * Issue is not observed on 7.0.1 * When uninstalling agent, don't delete the agent installation directory. |
| Description |
Original:
h3. Issue Summary
Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent This is reproducible on Data Center: Yes h3. Steps to Reproduce # Install Discovery agent # Update the token for the agent by copying token from discovery tool # Uninstall the agent and reinstall on the same machine # Configure the agent with the same token from Assets discovery h3. Expected Results # Agent should be identified by Discovery tool and status updated correctly. h3. Actual Results # Agent is identified by the Discovery tool, withe the message "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified." # The agent is unable to connect and transfer data to discovery. The below exception is thrown in the Discovery log file: {code:java} Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified. {code} The below exception is thrown in the Discovery log file: {code:java} [Error] Failed to decrypt credentials {code} h3. Workaround * Create a new token on discovery and update them on agents * Or, downgrade to 7.0.1 |
New:
h3. Issue Summary
Reinstalling Discovery agents with same token breaks connectivity between Discovery tool and Agent This is reproducible on Data Center: Yes h3. Steps to Reproduce # Install Discovery agent # Update the token for the agent by copying token from discovery tool # Uninstall the agent and reinstall on the same machine # Configure the agent with the same token from Assets discovery h3. Expected Results # Agent should be identified by Discovery tool and status updated correctly. h3. Actual Results # Agent is identified by the Discovery tool, withe the message "Unhealthy. Invalid network message signature. Message is corrupted or invalid agent token was specified." # The agent is unable to connect and transfer data to discovery. The below exception is thrown in the Discovery log file: {code:java} Stopping AgentClient to xxx.xxx.xxx.xx:xxxxx. Reason: Invalid network message signature. Message is corrupted or invalid agent token was specified. {code} The below exception is thrown in the Discovery log file: {code:java} [Error] Failed to decrypt credentials {code} !screenshot-1.png|thumbnail! h3. Workaround * Create a new token on discovery and update them on agents * Or, downgrade to 7.0.1 |
| Attachment | New: screenshot-1.png [ 460525 ] |