Skip to main content


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

Configure platform authentication with the basic credentials authentication service type (8.2)

Updated on May 3, 2021

The default authentication for Pega Platform™ uses a new type of authentication service. You can customize this service, as for any authentication service type.

All authentication services with the basic credentials type include mobile authentication with the OAuth 2.0 protocol and proof key for code exchange (PKCE). You no longer need to create a custom authentication service to support mobile applications.

Operator credentials can be verified using a data page instead of through the Pega Platform database. For example, you can authenticate external customers against a master customer file.

All authentication services provide new options for provisioning operators using a data transform instead of a model operator, to avoid storing unneeded operators in the database.

Basic authentication services also support features that are available to other authentication service types, including:

  • Provisioning new operators by using a model operator or data transform
  • Preauthentication and postauthentication activities
  • Custom property mapping
  • Easily selectable security policies

The image below shows the default Platform Authentication service.

Thumbnail

Default Platform Authentication service with the basic credentials type

For more information, see Configuring a basic authentication service.

  • Previous topic Protect against insecure deserialization (8.2)
  • Next topic Process personal client data securely with client-based access control

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