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

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

Setting up end user authentication

As a SaaS administrator, you can configure Remedy SSO to authenticate end users by using the following authentication methods:

  • AR
  • Certificate-based
  • LDAP
  • Local
  • Kerberos
  • OpenID Connect
  • Pre-authentication
  • SAML 2.0
Related blogs in BMC Communities

Securing Tomcat Server For Remedy Single Sign-On Open link

The following table describes the end-to-end tasks that you need to perform to configure any authentication in Remedy SSO.

TaskTask descriptionReference
1

If you have Remedy SSO in multitenant mode, if required, create a tenant, and switch to a Remedy SSO tenant in which you would like to configure authentication.

If you have a single default tenant, skip this task.

Setting up tenants
2

Configure the Remedy SSO server settings after you complete the installation of Remedy SSO application.

Configuring the Remedy SSO server
3

Add and configure a realm for which you want to configure an authentication method.

Adding and configuring realms


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

Comments

  1. Felipe Pineda

    The link "Securing Tomcat Server For Remedy Single Sign-On" is broken.

    Jul 28, 2021 01:30
    1. Ravee Panjwani

      Thanks for your comment, Felipe. It seems like we have a 404 on that one and will need to remove the URL.

      We have added some content to this topic, which we hope will help → Security planning#ConfiguringTomcatsecurity

      Thanks,
      Ravee

      Aug 13, 2021 01:10