Define the authorization and authentication strategies for your application.
- Proves to the application that you are who you say you are.
- Determines the functions that you can perform in the application. This corresponds to an access group and role configuration.
Security planning involves defining authorization and authentication strategies for your application. It is a best practice to create new access groups and roles that are based on the default access groups and roles that come with the product.
Security planning also involves setting up the organization structure and operator attributes. The application provides security in the form of access settings and denial rules. Many integration rules also incorporate authentication.
For more information about the additional aspects of security, enroll in the Lead System Architect course on Pega Academy.
- Authentication schemes
The Pega Platform offers the following authentication types:
- Implementing your authentication scheme
Your site can use a centralized, automated means of maintaining operator data instead of maintaining it manually in your application.
- Authorization scheme
Pega Retail Advisor comes with a predefined set of access groups, roles, and privileges. You can use the application roles as a starting point, but you should create your own application-specific access groups and roles to avoid any future problems when upgrading.
- Configuring your organization structure
Use the organization structure for routing and reporting within the application. Typically, the application organization structure does not map operators exactly to the site's organization chart but instead, it maps the work that those operators do.
- Operator attributes
An operator's access group affects what the operator can do in the application. In addition to the access group, the following fields in the operator record influence how the application handles assignment of work to the user.