Remedy Single Sign-On 20.08
Learn what’s new or changed for Remedy Single Sign-On version 20.08 including new features, urgent issues, documentation updates, and fixes or patches.
To stay informed of changes to this space, place a watch on this page.
The following updates have been added since the release of the space:
September 23, 2020
Remedy SSO 20.08 introduces the following features:
Manage user accounts who will have access to Remedy SSO.
Configure the maximum session time for end users, enable the account lockout for administrators and audit records.
Configure authentication of end users through a specified authentication method.
Set up administrator accounts, activate tenants, and secure sensitive data.
Set up integrations with other BMC products.
Resolve common issues or errors, review logs, or contact BMC Customer Support.
When you export a custom PDF, you can select the topics to include. For information about how you can export a custom PDF from this space, see Exporting to PDF and other formats.
Ready-made PDFs of this space
The following table lists topics that contain videos that supplement or replace the text-based documentation.
Here are some answers to the most frequently asked questions about the Remedy Single Sign-On product.
Frequently asked questions about Remedy Single Sign-On
Identity providers do not automatically notify Remedy SSO about the password change. Hence, an end user's Remedy SSO session remains active until it expires, and is not revoked after password change on IdP. To force the logoff, and receive the request for entering a new password, an end user needs to ask a Remedy SSO administrator to delete all active sessions/OAuth of this end user.
You can change your password in the Remedy SSO Admin Console, in the Admin User Management. To change your password, select your user account name, and then edit your password as required. See Setting up Remedy SSO administrator accounts for more details about how to change the password of an administrator.
You can obtain the Remedy SSO server version information through the <RSSO Server>/config/server-status URL. You must be authenticated as a Remedy SSO administrator before that.
Yes, you can do this.
If the OpenID Issuer URL is configured for the OAuth 2.0, developers of third-party applications can retrieve the OAuth metadata from the Remedy SSO server by using the following autodiscovery URL: RSSO_host:RSSO_port/rsso/.well-known/openid-configuration.
Running this request in the browser window returns details about the OpenID Connect provider's configuration, including the URIs of the authorization, token, revocation, userinfo, and public-keys endpoints.
Multi-factor authentication is not implemented on the Remedy SSO side. Remedy SSO only supports scenarios where the Identity Provider that is configured in Remedy SSO for authentication has configured multi-factor authentication.
For example, if your application is integrated with the Remedy SSO server that is configured to use the SAML protocol to authenticate users accessing an application, then for the end users to pass the authentication flow, multi-factor authentication must be enabled and configured on the SAML Identity Provider.
You can check whether an earlier version of your product is compatible with Remedy SSO 20.08 on the page.
You can enable audit records for end-user events in the Remedy SSO Admin Console > General > Advanced > select the End-user events check box.