Can TrueSight Orchestration use a custom cookie name in Remedy Single Sign-On?

Version 1
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    BMC Atrium Orchestrator Platform


    BMC Atrium Orchestrator Platform


    BMC Atrium Orchestrator Platform BMC Atrium Orchestrator Platform 8.x.xx TrueSight Orchestration Platform 8.x.xx


    BMC Remedy Single Sign-On (RSSO) uses the default cookie name "sso_xxxxxx". If an administrator changes this to a different cookie name, like "tso_grid_xxxx", no users can log into BMC Atrium Orchestrator / TrueSight Orchestration (TSO). The logs suggest that RSSO is rejecting the cookie. Can TSO use a custom cookie name?



    TSO uses a configuration setting to determine the cookie name it uses. If you change your cookie name in RSSO, you must also change it in TSO. Open the file [TSO_HOME]\config\authentication.xml and add the element "token-name".




    After this change, authentication.xml should look like this::


    <?xml version="1.0" encoding="ISO-8859-1"?><authentication>


    Save the file and restart TSO. The peer will read the cookie name during startup and use the new name when it communicates with RSSO.


    Article Number:


    Article Type:


      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles