"Missing valid CSR" error displayed in TIBCO Spotfire Server administrator interface while trusting the Node

"Missing valid CSR" error displayed in TIBCO Spotfire Server administrator interface while trusting the Node

book

Article ID: KB0076310

calendar_today

Updated On:

Products Versions
Spotfire Server 7.5 and higher

Description

While trusting an untrusted node in the TIBCO Spotfire Server administrator web interface > Nodes & Services > Untrusted nodes, a red pop-up might come up showing "Missing valid CSR" error. 

This error can be seen if there is an issue establishing the trust between the TIBCO Spotfire Server and the Spotfire Node Manager using the certificates located under "[Spotfire server installation directory]\nm\trust" and "[Spotfire Node Manager installation directory]\nm\trust". This is most often seen when the trust is revoked for a node and that the node cannot communicate anymore without a new CSR submitted and the keystore recreated.

Issue/Introduction

"Missing valid CSR" error displayed in TIBCO Spotfire Server administrator interface while trusting the Node

Environment

All

Resolution

To make sure that the trust can be established to setup a connection between the TIBCO Spotfire Server and the Node Manager, the following steps should be performed:
  1.  Stop the TIBCO Spotfire Node Manager service.
  2. Log in to Spotfire Administrator UI.
  3. Go to Nodes & Services > Untrusted nodes
  4. Delete the node available here.
  5. Stop the TIBCO Spotfire Server service.
  6. On the Spotfire Server, go to Spotfire server installation directory\tibco\tss\version\nm\trust" and delete the certificate here.
  7. On the Node Manager server, go to "Spotfire Node Manager installation directory\tibco\tsnm\version\nm\trust" and delete the certificate here.
  8. Start the TIBCO Spotfire Server service.
  9. Start the TIBCO Spotfire Node Manager service.
  10. Log in to Spotfire Administrator UI, go to "Nodes & Services > Untrusted nodes" and wait for the node to show up.
  11. Once the node shows up in the "Untrusted Nodes", trust the node.
If there is no other issues, the node should be trusted now and should be up and running.

Additional Information

Doc: Trusting a node
Powered by Wolken Software