KB47766: How to setup a trust relationship for MicroStrategy Office against an Intelligence Server cluster.

 
Sample Code/Error

There is no trust token for this web server. Please contact the administrator.

 
For steps on how to enable trusted authentication for Strategy Office / Web Services, refer to KB41359 - How to configure Trusted Authentication for MicroStrategy Office 9.2.x and later.
 
In a non-clustered environment, a trust token is generated to uniquely identify a trusted web server. This trust token is stored in the metadata on Intelligence Server side. The web server stores the token for the Intelligence Server in a token file, called ".token" under the Strategy Web Services root deployment directory. 
 
As outlined in technical note KB41359, a session with Intelligence Server must be established before a trust relationship can be created through the Strategy Office configuration interface. The reason for this being the need to write the token into the metadata.
 
In a clustered environment, this initial session to create a trust relationship is established on any of the Intelligence Server nodes thanks to Intelligence Server load balancing. Therefore, when creating the trust relationship the token file will be named according to the Intelligence Server of the current session.
 
For example, when creating an initial session on WS1 using Standard authentication, a Strategy session was created on Intelligence Server node 2 (I-SERVER_2). When creating the trust relationship through Strategy Office, the token for WS1 will be written into the common metadata for both Intelligence Server nodes. However, the token file created on the web server will be named I-SERVER_2.token.