This documentation supports the 19.08 version of Remedy Single Sign-On.

To view an earlier version, select the version from the Product version menu.

Configuring after upgrade

After you upgrade Remedy Single Sign-On, perform the tasks described in this topic.

To configure Remedy SSO server after upgrade

  1. If before upgrade you modified the original web.xml located in <RSSO Tomcat>\webapps\rsso\WEB-INF folder on the Remedy SSO server, then you need to update the upgraded file with your custom settings.

  2. If your system had realms configured for SAML authentication, reconfigure the SAML authentication settings.

  3. If your system had the Tenant field configured for some the realms,  configure the Digital Service Management page to show applications.
  4. Configure the Digital Service Management page to show applications as required. 

To update SAML SP metadata template

  1. Log in to Remedy SSO Admin Console.

  2. Navigate to Realm > Authentication, and select SAML type of authentication.
  3. For all realms with SAML type of authentication, update the SP metadata template. To access the edit mode of the SP metadata, in the Template section, click Edit

    The original SP metadata template is the following:

    SP metadata template
    <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
    <EntityDescriptor entityID="%%ISSUER%%" xmlns="urn:oasis:names:tc:SAML:2.0:metadata">
        <SPSSODescriptor AuthnRequestsSigned="%%SIGN_REQUEST%%" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
            <KeyDescriptor use="signing">
                <KeyInfo xmlns="">
            <KeyDescriptor use="encryption">
                <KeyInfo xmlns="">
            <SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings: HTTP-POST" Location="%%LOGOUT_REQUEST%%" ResponseLocation="%%LOGOUT_RESPONSE%%" />
            <AssertionConsumerService index="0" isDefault="true" Binding="urn:oasis:names:tc: SAML:2.0:bindings:HTTP-POST" Location="%%CONSUMER%%" />
    1. If you enabled the IdP initiated single logout feature, include the following information in the SP metadata template after the <AssertionConsumerService> tag:

      <SingleLogoutService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="%%LOGOUT_REQUEST%%" ResponseLocation="%%LOGOUT_RESPONSE%%" />

      • Location is the endpoint for the identity provider to send the logout request. For example,
      • ResponseLocation is the endpoint for the identity provider to send the logout response after getting the logout request from Remedy SSO. For example,

    2. To sign up the SP metadata, update the following tag as follows:

      <EntityDescriptor entityID="%%ISSUER%%" xmlns="urn:oasis:names:tc:SAML:2.0:metadata" %%METADATA_ID%%>
  4. Update Remedy SSO (SP) metadata on the identity provider side.

To configure the Digital Service Management page to show applications


This note is applicable for Remedy SSO upgrade documentation 19.11 and later.

Perform this step if you upgrade Remedy SSO from version earlier than 19.08.

If before upgrade of Remedy SSO, some of the realms had the Tenant field configured, users who belong to this realm, after upgrade will not see these applications from the domain associated with this realm.
If you want to preserve the behavior before upgrade, you must configure the Tenant field on the Launchpad page for these applications. For information about how to do this, see Adding applications to the Digital Service Management page.

Where to go from here

Now, when you have configured Remedy SSO after upgrade, you can check the upgrade was successful. For information about how to do this, see Verifying the installation.

Was this page helpful? Yes No Submitting... Thank you