Support for encrypted traffic in a cluster
Valid from Pega Version 7.3
The Pega 7 Platform includes the Ignite platform, which supports encryption for intra-cluster communications. You can now configure encryption for intra-cluster traffic for compliance with regulatory or organizational security requirements.
For more information, see Enabling encrypted traffic between nodes.
Deploy revisions directly in target environments
Valid from Pega Version 7.3
As a revision manager, you can now directly deploy or migrate completed revisions to multiple Pega 7 Platform environments that were configured as targets by the system architect. The revision management process is faster because you do not need to package a revision as a JAR file, and then manually import that file to the Pega 7 Platform. Additionally, this solution gives business users more control over application rulesets and enables them to act more independently.
For more information, see Direct deployment of revisions.
Delegation experience in revision management
Valid from Pega Version 7.3
Revision managers can now control rule authoring by assigning a delegation experience to any rule that is part of a revision management change request. Delegation experience types offer different rule authoring capabilities, so the revision manager can select the appropriate delegation experience for the task and the strategy designer’s experience.
Monitor standard and custom security events
Valid from Pega Version 7.3
From the new Security Event Configuration landing page, you can select the standard and custom security events that you want the Pega 7 Platform to log automatically for every user session. The security events are grouped into the following types:
- Authentication
- Data access
- Security administration
- Custom
The API logCustomEvent() is provided so that you can create custom security events that are specific to your applications and that can be monitored by the Pega 7 Platform. For more information, see Security Event Configuration.
File data set
Valid from Pega Version 7.3
You can now create a File data set that reads data from a file that is in CSV or JSON format. You can use this type of data set to test data flows and strategies.
For more information, see Creating a File data set record.
SAML configuration supports global resource settings
Valid from Pega Version 7.3
In the SAML Authentication Service form, you can now use global resource settings, which allow greater flexibility for values that change compared to using fixed text values. Apply global resource settings, which are dynamic values, in the Identity Provider (IdP) information section and the Service Provider (SP) settings section of the form.
For more information, see Authentication Service form - Completing the SAML 2.0 tab.
Restrict visibility of scalar property values for certain users
Valid from Pega Version 7.3
You can use the Access Control Policy rule to mask individual scalar property values from specified users. You can restrict visibility for the following property types:
- DateTime
- Integer
- Text
For more information, see Masking property visibility for users.
Disable inactive operators
Valid from Pega Version 7.3
As a system administrator, you can control access to an application by disabling Operator IDs. To disable an Operator ID, you can use one of the following options in Designer Studio:
- Call the Service REST: user.
- Change settings on the Operator Access tab on the System Settings landing page or on the Security tab on the Operator ID form.
- Define the number of inactive days in the security policies before an Operator ID is automatically disabled.
For more information, see System Settings - Operator Access tab, Enabling Security Policies, Security tab on the Operator ID form.
Security landing pages and features require privileges
Valid from Pega Version 7.3
Security-related landing pages and features are no longer visible and accessible to every user. To view and configure the following security features, you must have the appropriate privileges:
- Attribute-based access control (ABAC) policies require the pzCanManageSecurityPolicies privilege.
- The Authentication Services landing page requires the pzCanCreateAuthService privilege.
Authenticate users in processes with a JSON Web Token
Valid from Pega Version 7.3
You can generate and process a JSON Web Token (JWT) in Pega® Platform to secure communications in Pega Platform applications. JWTs are intended to securely transmit small amounts of information between two parties. Because the JWT is signed, the integrity of the information is assured. The contents of the JWT can be used to authenticate a user or to exchange information.
For more information, see Token Profile data instance.