Define the authorization and authentication strategies for your application. Authentication proves to the application that you are who you say you are. Authorization 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.
The following topics are included in this section:
- Implementing the security model and organization structure
- Configuring your organization structure
- Authentication schemes
- Authorization scheme
- Operator attributes
Implementing the security model and organization structure
After you review the existing groups and roles to determine additional groups and roles that you need, create them in Dev Studio when logged in as an administrator.
- For Access groups, click .
- For Access roles, click .
Defining the 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.
- In the header of Dev Studio, click .
- Review the existing structure.
- Determine the organization, division, and unit levels of the hierarchy.
The Pega Platform offers the following authentication types:
- Based on passwords in the Operator ID data instances and the login form. This is defined by the HTML @baseclass.Web-Login rule, which your application can override.
- Similar to PRBasic, but passes credentials by using Secure Sockets Layer (SSL) with Basic HTTP authentication. The login form is defined by the HTML @baseclass.Web-Login-SecuredBasic rule, which your application can override.
- Supports access to an external LDAP directory or a custom authentication scheme.
- Supports external assignments (Directed Web Access).
- Specifies that the application server in which the Pega Platform is deployed uses JAAS to authenticate users.
Defining the 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.
For more information, see Operators.
Defining the operator work group
The work group setting in the operator record affects how your application delivers work to the operator. Review the Operator record and determine the rules for assigning a work group to an operator or the role that multiple operators hold.
- In the header of Dev Studio, click .
- Select an operator ID.
- On the Work tab, review the work group information for the operator record.
- Determine your policy for assigning a work group to an operator or the role that multiple operators hold.For more information, see Fields for operator work groups, work queues, and schedules.
Defining the operator skills
Skill settings in the operator record affect how the application routes work to the operator. Skill settings also affect how the application gets the most appropriate work when using the Get Next Work feature. You must determine the skills that are appropriate for your application and operators.
- Define the skills that are needed for the application.
- Determine which operator records or roles should be associated with those skills.
Defining the operator calendar
The application calendar affects date calculations within the application, such as the date between business days calculation, and the SLA goal and deadline date calculation. The calendar on the operator record is relevant only if you have users who are not working in the same time zone as the rest of the organization. Otherwise, the application uses the calendar on the organization record and you can skip this step.
- Determine the calendar instances that are needed for your application.
- Determine which operator roles need a distinct calendar.
- Determine the operator location.For more information, see Specifying calendar navigation options.