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

To view the latest version, select the version from the Product version menu.

18.08 enhancements

This section contains information about enhancements in Remedy Single Sign-On (Remedy SSO) version 18.08.



Ability to use HTML to customize the end user login page

As a Remedy Single Sign-On administrator, you can use HTML to customize the end user login page. This provides an ability to embed an URL to the Intranet portal or to reset the password from the end user login page. For this, enter the required HTML code for the login page in the Extended Login page information (html) field under the Branding sub-tab.

For more information, see Rebranding the end user login page.

Ability to configure the number of simultaneous logins

You can now control the number of simultaneous logins per user (per realm) by adding the required number of session quota for a particular realm. You can also decide whether to invalidate the older session or not let the user log in to a new session based on the number of logins allowed.

For more information about session quota, see Configuring realms. For information about troubleshooting, see Troubleshooting log on and log off issues.

Admin User Management by configuring multiple administrator accounts

As an RSSO administrator, you can now use your administrator account to create multiple RSSO administrator accounts in your organization so that each administrator has their own login. In the Admin User Management tab, you can manage the accounts, such as removing accounts or locking and unlocking accounts.

For more information, see Setting up Remedy SSO administrator accounts.

RSSO administration account lockout policy configuration setting

As a RSSO administrator, once you add multiple administrators, you can block the accounts of those administrators through the Remedy SSO Admin console. At a server level, you can set the number of incorrect password attempts by an RSSO administrator account before the account gets locked out. This is for security purposes to make sure that there are no unauthorized logins. Additionally, you can also unblock the locked administrator accounts manually through the Admin User Management tab on the Remedy SSO Admin Console.

For more information, see Remedy SSO server general configuration.

Support for cross launching applications integrated with different RSSO servers

You can enable single sign-on when users cross launch and access an application from another application through Iframe even though the applications are deployed on two different RSSO servers. The application on the originating server constructs a URL to initiate cross launch of the the target application on the target RSSO server.

To allow the originating application to open target application through Iframe, a new field, ALLOW-FROM Domain(s), is added on the Realm > Authentication tab in the Remedy SSO Admin console. For more information, see Configuring the pre-authentication mechanism and Enabling cross launch for applications integrated with different RSSO servers.

Configuring multiple redirect URLs for OAuth authentication

As a RSSO administrator, you can configure the OAuth authentication by adding multiple URIs, so that the client can be redirected to different URLs. You do not have to deploy the each individual client multiple times for different URLs.

For more information, see Configuring OAuth 2.0.

What's changed in this release

EnhancementProduct behavior in versions earlier than 18.08Product behavior in version 18.08

Admin User Management by configuring multiple administrator accounts

Only one administrator could be added for the RSSO server.

As an administrator, you can add multiple administrator accounts.

RSSO administration account lockout policy configuration setting

You could not lock out an administrator account.As an administrator, you can unblock the accounts of those administrators who exceed the number of login attempts due to incorrect password and whose accounts have been blocked. Additionally, you can also manually block/unblock the locked administrators through the Admin User Management tab on the Remedy SSO Admin Console.
Setting the timeout for an administrator sessionYou could not specify the time after which the administrator login session would timeout.You can now specify the timeout for an administrator session. For this, a new field, Max Admin Session Time has been added to the Remedy SSO Admin console under the General > Basic tab. For more information, see Remedy SSO server general configuration.
Retaining the parameters in the URL for SAMLv2 authenticationWhen you entered any URL, the parameters that you entered after the # sign were removed during the verification of the link during the SAMLv2 authentication process.

The parameters in the URL after the # sign are retained during the SAMLv2 authentication process.

Creating multiple groups with similar namesWhen you created more than one group with a similar name, for example, one group uses " " and the other uses "_", Remedy Single Sign-On considered them as the same group.Now, even if the groups have similar names, Remedy Single Sign-On considers them as separate groups.
Logout URL When the Remedy SSO agent triggered the logout flow, if a callback-url parameter was present, Remedy SSO immediately redirected the end user to the specified callback URL after the completion of the logout process.

When the Remedy SSO agent triggers the logout flow, if a callback-url parameter is present, Remedy SSO redirects the end user only to the same domain as the application.

For example: If the application domain is bmc.com, any combination of <url>.bmc.com is allowed.

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

Comments