About Authentication Service data instances

New

Service

Mapping

Custom

History

More...

Purpose

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

• Use a Lightweight Directory Access Protocol (LDAP)-compliant directory server to authenticate the Process Commander users.
• Use some other vendor-specific security solution to authenticate the Process Commander users.
• Implement single sign-on.

Complete two main steps when using this feature:

1. Create an authentication service data instance that identifies activities that override the default Process Commander authentication process. If your goal is to configure Process Commander to use an LDAP-compliant directory server to authenticate users, use the Authentication accelerator. See About the Authentication accelerator.
2. Insert a servlet definition element and a servlet-mapping element in the Process Commander web.xml file that identifies the name of the authentication service.

When initially installed, the web.xml file contains three servlet definitions you can use for authentication service implementations: WebLDAP1 to WebLDAP3. By choosing an authentication service name that matches one of these, you can implement up to three without changing the web.xml file and without redeploying Process Commander.

For information about configuring and using authentication services, see Authentication in PegaRULES Process Commander, a document available from the Integration area of the Pega Developer Network.

Category

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

Atlas — Initial Authentication Service data instances

SysAdmin category
Home