Enabling multi-domain support for the Presentation Server in Remedy SSO

Follow these instructions to enable multi-domain support for the TrueSight Presentation Server configured to work with the Remedy SSO version 19.02 or later:

To enable multi-domain support for TrueSight Presentation Server and Infrastructure Management server

1. Configure Remedy SSO for Presentation Server and Infrastructure Management server applications hosted on different domains and note down the OAuth Client ID that was pre-populated when you configure the OAuth. For more information, see Configuring multiple domain support in the Remedy SSO documentation in docs.bmc.com. .

   Notes

   1. Use the Presentation Server and Infrastructure Management server URI while registering the OAuth client in Remedy SSO server using the pattern: http(s)://<application.domain>:[port]/[path]/_rsso/oauth/callback.

   2. Update the Remedy SSO agent properties file from the following location:

      (Linux) 

      • (Presentation Server) <Install_directory>/truesightpserver/modules/tomcat/webapps/ROOT/WEB-INF/classes/rsso-agent.properties 

      • (Infrastructure Management server) <Install_directory>/pw/tomcat/webapps/pronto/WEB-INF/classes/rsso-agent.properties 

      (Windows) 

      • (Presentation Server) <Install_directory>\truesightpserver\modules\tomcat\webapps\ROOT\WEB-INF\classes\rsso-agent.properties 

      • (Infrastructure Management server) <Install_directory>\pw\tomcat\webapps\pronto\WEB-INF\classes\rsso-agent.properties 

2. Log into the Presentation Server or Infrastructure Management server and download the GenerateCookieName.zip file to a folder of your choice and unzip it. 

3. From the command prompt, navigate to the following directory:

   • (Linux) <install_directory>/jre/bin

   • (Windows) <install_directory>\jre\bin

4. Run the following command to generate the cookie name: 

   Note: Use the oauth-client-id that you noted down when you configured the OAuth. See, step#1 for details.

   (Linux)

   java -jar <download_folder in step 2>/GenerateCookieName.jar <oauth-client-id>

   (Windows)

   java -jar <download_folder in step 2>\GenerateCookieName.jar <oauth-client-id>

5. Log into the Remedy SSO admin console and and navigate to General > Advanced > Cookie Name and add the newly generated cookie name from the above step.

6. Log into the Infrastructure Management server.

7. Back up the following file and folder on the Infrastructure Management server:

   • (Linux) 

     • <Install_directory>/pw/apache/conf/extra/httpd-proxy.conf

     • <Install_directory>/pw/tomcat/webapps/pronto/WEB-INF/lib/

   • (Windows) 

     • <Install_directory>\pw\tomcat\webapps\pronto\WEB-INF\lib\

     • <Install_directory>\pw\apache\conf\extra\httpd-proxy.conf

8. Update the httpd-proxy.conf file with the following entries:

   • (Linux) <Install_directory>/pw/apache/conf/extra/httpd-proxy.conf

   • (Windows) <Install_directory>\pw\apache\conf\extra\httpd-proxy.conf

   Entries to add

   ProxyPass /_rsso/ ajp://localhost:8009/_rsso/
   
   ProxyPassReverse /_rsso/ ajp://localhost:8009/_rsso/

9. Copy the following files from Remedy SSO Server to the Infrastructure Management server (Standalone or both the Primary and Secondary nodes of a HA setup):

   (Copy from) Remedy SSO Server: 

   • (Linux) <Install_directory>/ apache-tomcat-<ver>/webapps/rsso/WEB-INF/lib/

   • (Windows) <Install_directory>\apache-tomcat-<ver>\webapps\rsso\WEB-INF\lib\

   (Copy to) Infrastructure Management server: 

   • (Linux) <Install_directory>/pw/tomcat/webapps/pronto/WEB-INF/lib/

   • (Windows) <Install_directory>\pw\tomcat\webapps\pronto\WEB-INF\lib\

   Files to be copied from Remedy SSO Server:

   • json-xxxxx.jar
   • slf4j-api-xxxxx.jar
   • jackson-annotations-xxxxx.jar
   • jackson-core-xxxxx.jar
   • jackson-databind-xxxxx.jar

10. (Only HA setup) On both the primary and secondary nodes of Infrastructure Management server, add the following entry in the Pronet.conf file
    pronet.tsim.proxy.hosts=<FQDN of the Infrastructure_Management_Server Load Balancer that is different from the Infrastructure_Management_Server Domain>

11. Restart the Infrastructure Management server.
12. Ensure that the clocks of the Remedy SSO server, Presentation Server, and Infrastructure Management server are in synchronization with their respective time zones.