Pega Sub Report is a Report Definition feature that enables users to create a master report and derive a “child” or “sub-report” from the main report for additional granularity. The sub-report provides additional context and detail to the primary report, and helps identify and analyze data more efficiently by allowing users to drill down into the results.
Pega RBAC (Role-Based Access Control) is a security feature of Pega Platform that authorizes users to Pega application functions based on their assigned roles. It assigns permissions and access control to roles that are used to control user access. RBAC is based on the concept of a "role" as it applies to an individual's relationship to an application or system, and the access and privileges associated with it. RBAC provides administrators with the ability to quickly grant and revoke access and securely manage users throughout an organization.
Pega ABAC (Attribute Based Access Control) is a model used to control user access to information in an enterprise system. It uses attributes associated with the user, the resource, and the environment in order to determine which users should be authorized or denied access to a resource. Pega ABAC also makes use of policies and rules to determine the level of access a user should have.
Pega Security is the system of tools, policies, user roles, and processes used to define and protect the use and management of the Pega platform and its data. Pega Security is designed to detect, prevent, and respond to security threats, risks, and attacks to the Pega platform, data, and applications. It also helps to ensure the privacy, integrity, and availability of customer data.
Pega Connect-REST supports multiple authentication schemes, including OAuth2, basic authentication headers, and custom headers.
OAuth2 is recommended for authenticated applications.
Basic authentication can be used if user identities are required, but these types of applications are often vulnerable to attack and require additional security measures.
Custom headers can be used to provide session-based authentication, where the header is passed with each request and contains authentication information.
Custom headers require additional development effort, but can provide more control over authentication and greatly improve security.
Authentication Profile in Pega Connect-REST allows for access to Secured REST services by specifying the credentials and security protocols. The profile is used to authenticate requests to external systems or access OAuth2 and OpenID Connect services for user-level authentication. Authentication Profile procedures can be configured to support Basic Authentication, OAuth2, and OpenID Connect protocols.
The authentication Profile in Pega Connect-REST is a set of configurations that defines the authentication mechanism and information used to authenticate an external system with the Connect-REST service. It includes a number of authentication details such as authentication type, trust store, user ID, password, OAuth configuration, and so on. An authentication profile also allows users to securely store and manage authentication tokens used in token-based authentication.
#security
