KB440975: How to configure MicroStrategy Library to communicate through SSL Encryption to an Intelligence Server with SSL Encryption Enabled

Description

Strategy  Library application allows users to access their Strategy analytics from multiple devices as well as allowing users to collaborate across their organization. To ensure your enterprise data is secure, Library supports the ability to leverage SSL encryption. This article is meant to provide instructions to configure Library with SSL encryption of communications to an Intelligence Server with SSL encryption already setup/enabled.

Prerequisites

Before starting, ensure that you have already configured the I-Server to use SSL Encryption following documentation for configuring secure communication.

Instructions

In order to correctly configure the Strategy Library application to communicate to an I-Server that has SSL enabled, you must first go to the following file path located on the machine hosting Strategy Library:

\<Web Server path>\webapps\StrategyLibrary\WEB-INF\classes\config

 
Within this folder, there are two files: configDefaults and configOverride properties files. These properties files should be referenced in the above file path, the first being the configDefaults.properties file. Use the configDefaults.properties file as a reference to modify the configOverride properties file as described below.

Step 1:

configDefaults.properties:

# Description: {true | false} Controls whether the communication between Web Server and IServer uses TLS or not.
#    If true, then the trustStore.path file must be populated with the public certificate for theIServer machine.
# Default: false
# Example: iserver.tlsEnabled=false
iserver.tlsEnabled=false

#SSL/TLS TrustStore configuration
# Description: {RELATIVE PATH} If TLS is enabled between the RESTful API Server to the Collaboration Service or IServer, then a Trust Store
#    The relative path (inside the WAR file) to the Trust Store file
#     Also, supports Optional prefix "classpath:" (for a class path resource) or "file:" (for an absolute path) 
#   ex. classpath:config/truststore.pfx or file:/tmp/truststore.pfx
#     Refer to http://docs.spring.io/spring-framework/docs/current/javadoc-api/org/springframework/core/io/ResourceLoader.html#getResource-java.lang.String-
# Default: NONE
# Example: trustStore.path=/WEB-INF/truststore.pfx
trustStore.path=

# Description: {TEXT} The passphrase used in the construction of the Trust Store file
# Default:
# Example: trustStore.passphrase=randomPassword
trustStore.passphrase=

 
In the configOverride.properties file, add the following lines based on the above configDefaults file (changes made in bold):

iserver.default.port = 34952
iserver.tlsEnabled=true
trustStore.path=(insert your truststore path here)
trustStore.passphrase= (insert the cert passphrase here)
iserver.maxPoolSize = 100
session.searchWorkingSet = 3
iserver.default.hostname = db1011
iserver.initialPoolSize = 10
session.workingSet = 10
iserver.requestTimeout = 120000
auth.modes.available = 1
auth.modes.default = 1
services.StrategyWeb.baseURL = https:/...../Strategy/servlet/mstrWeb
#
# Use this file to override default properties configured in configDefaults.properties.
# Changes made in this file would be kept during upgrade process.
#
# ex. auth.modes.available=1
#

 

Note:****All changes made to the files provided above must match all case sensitivity.

Step 2

To apply these changes, restart your web application.
 
Third Party Software Installation: WARNING:
The third-party product(s) discussed in this technical note is manufactured by vendors independent of Strategy. Strategy makes no warranty, express, implied or otherwise, regarding this product, including its performance or reliability.
KB440975