About Authentication Services

You are here: Reference > Data classes > Authentication Service data instances

About Authentication Services
About New Service SAML 2.0 Mapping Custom History More...

The Authentication Service feature enables you to override the default authentication process. Use an authentication service when you want to configure Pega 7 to do one of the following:

Implement SAML web single sign-on, or another single sign-on mechanism.
Use a Lightweight Directory Access Protocol (LDAP)-compliant directory server to authenticate Pega 7 users.
Use some other vendor-specific security solution to authenticate Pega 7 users.

Complete one of these actions when using this feature:

Create an authentication service data instance that identifies activities that override one of the default Pega 7 authentication processes (see below).
Insert a servlet definition element and a servlet-mapping element in the Pega 7 web.xml file that identify the name of a new authentication service.

Note: When you install Pega 7, the web.xml file contains sample servlet definitions you can use to implement authentication services:

SSO, SSO1, or SSO2 for authenticating users using SAML Web SSO.
WebLDAP1, WebLDAP2, or WebLDAP3 for authenticating users using LDAP.

If you use these authentication service names you avoid having to change the web.xml file and redeploy Pega 7.

For information about configuring and using authentication services, see PDN article Authentication in PegaRULES Process Commander.

Category

Authentication services are instances of the Data-Admin-AuthService class. They belong to the SysAdmin category.