×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')
BMC TrueSight Presentation Server 11.3 ... Administering Managing users and access control Managing users and user groups

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:

Notes

  • You must have installed the latest cumulative hotfixes for Remedy SSO version 19.02 or later. Contact BMC Support to obtain the hotfixes.
  • These instructions are applicable only if the domain name of either Presentation Server or the Infrastructure Management server or both are different from the Remedy SSO server domain name. For example, the <presentation_server>.abc.hr.com and <remedy_sso>.xyz.it.com.
Related topics

Setting up the Remedy SSO server Open link

Configuring tenants in Remedy SSO

Configuring user authentication for the Presentation Server in Remedy SSO

To enable multi-domain support for TrueSight Presentation Server and Infrastructure Management server (applicable only to version 11.3.03 or later)

  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 (19.02) Open link  or  Configure Remedy SSO for applications hosted on different domains (19.05 and later) Open link

    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.

To enable multi-domain support for TrueSight Presentation Server and Infrastructure Management server (applicable only to version 11.3.02)

  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 (19.02) Open link  or  Configure Remedy SSO for applications hosted on different domains (19.05 and later) Open link

    Note

    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 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 Presentation Server and Infrastructure Management server (Standalone or both the Primary and Secondary nodes of a HA setup):

    Presentation Server filesInfrastructure Management server files

    (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) Presentation Server: 

    • (Linux) 
      <Install_directory>/truesightpserver/modules/tomcat/webapps/ROOT/WEB-INF/lib/

    • (Windows) 
      <Install_directory>\truesightpserver\modules\tomcat\webapps\ROOT\WEB-INF\lib

    Files to be copied from Remedy SSO Server:

    • jjwt-api-xxxx.jar

    • jjwt-impl-xxxx.jar

    • jjwt-jackson-xxxxx.jar

    • org.apache.oltu.oauth2.client-xxxx.jar

    (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:

    • caffeine-xxxxx.jar
    • jjwt-impl-xxxxx.jar
    • org.apache.oltu.oauth2.client-xxxxx.jar
    • jjwt-jackson-xxxxx.jar
    • jjwt-api-xxxxx.jar
    • 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

  11. pronet.tsim.proxy.hosts=<FQDN of the Infrastructure_Management_Server Load Balancer that is different from the Infrastructure_Management_Server Domain>

  12. Restart the Presentation Server and Infrastructure Management server.
  13. Ensure that the clocks of the Remedy SSO server, Presentation Server, and Infrastructure Management server are in synchronization with their respective time zones.
Was this page helpful? Yes No Submitting... Thank you
Last modified by Harihara Subramanian on Apr 26, 2020
concept security administration access_control authentication tenants remedy_sso

Comments

  1. Utkarsh Kamat Shankhwalkar

    Content missing: Clicking on the 'GenerateCookieName.zip' link in TrueSight v11.3.03 section does not download the file but just reloads the page.

    Apr 26, 2020 09:46

Log in or register to comment.

Configuring tenants for the Presentation Server in Remedy SSO
Configuring user authentication for the Presentation Server in Remedy SSO
© Copyright 2014 - 2019 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.