This documentation supports the 20.08 version of Remedy Single Sign-On, which is available only to BMC Helix subscribers (SaaS).To view an earlier version, select the version from the Product version menu.

Configuring authentication

This section describes the types of authentication that you can use to configure authentication for a realm on the Remedy Single Sign-On server.

Related topics

Adding-and-configuring-realms

Single-sign-on-authentication-methods

Authentication type

Description

Reference

AR

With AR authentication, end users are authenticated through the Remedy AR System identity provider.

Cert

Certificate-based authentication uses a public key and a digital certificate to authenticate end users. 

Kerberos

The Kerberos protocol uses secret-key cryptography to provide a secure communication over a non-secure network. With Kerberos authentication, end users are only prompted once for their user ID and password.

LDAP

With LDAP authentication, end users are authenticated through an external LDAP directory.

Local

With Local authentication, the Remedy SSO server functions as an identity provider, and users stored locally in the Remedy SSO database are authenticated.

OIDC

OpenID Connect authentication is an extension to the OAuth 2.0 protocol. It provides information about an end user in a form of an ID token that verifies the identity of the end user.

Preauth

With preauthentication method, end users who have already been authenticated though another authentication provider are authenticated.

SAML

SAML 2.0 checks users identity and credentials. SAML 2.0 informs the service provider what access to grant to the authenticated user.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*