Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Identifying the operator for Kerberos authentication services

Updated on March 15, 2022

Specify the operator mapping so that a Kerberos authentication service can find the requestor record in your repository and bring values back to Pega Platform.

  1. Open the service from the navigation panel in Dev Studio by clicking RecordsSysAdminAuthentication Service and choosing a service from the instance list, and then navigate to the Kerberos tab.
  2. If you are using LDAP, in the User principal name attribute field, enter the LDAP attribute name that is used for the User Principal Name on the LDAP server.
  3. On the Mapping tab, map the naming attributes in the directory sever that correspond to the operator ID properties.
    1. Click the Add item icon, and add four attribute mapping rows.
    2. In the Property Name field, enter one of the following properties: .pyUserName, .pyOrganization, .pyOrgDivision, and .pyOrgUnit.
    3. In the Attribute Name field, enter the LDAP attribute that relates to the entered operator property.
  4. On the Custom tab, in the Source of operator credentials list, select where the operator credentials are stored.
    • Use credentials stored in PegaRULES – Only the users whose operator ID records do not have Use external authentication selected are allowed access through this service.
    • Use externally stored credentials – Only the users whose operator ID records have Use external authentication selected are allowed access through this service.
  5. Click Save.
  • Previous topic Configuring login using a Kerberos authentication service
  • Next topic Configuring the challenge behavior for custom or Kerberos authentication services

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us