Authentication, authorization and RBAC
Original learning guide · Pega ’25 path · Content v1.0.0
Learning objectives
- Explain authentication, authorization and rbac in the context of a loan application.
- Identify the configuration decisions and test an expected outcome.
- Recognize a common mistake before it affects users.
Understand the concept
Authentication verifies who a user is. Authorization evaluates what they may do. Role-based access control groups permissions by responsibility, but record and context restrictions may still apply to the authorized role.
Authentication establishes identity. Authorization determines allowed actions and data access. Operators identify people or system identities; access groups connect users to application context and access roles. Roles and privileges express permission. Apply least privilege and review the Security Checklist as part of deployment readiness.
Write one failed-authentication test and one authenticated-but-forbidden approval test. Explain why their expected outcomes differ.
A configuration example
A loan officer can collect and submit an application. A credit reviewer can assess it. Only an authorized approver can approve it. Test each role with both allowed and forbidden actions, including direct requests rather than only visible menus.
Application: Loan Origination Case type: Loan Request Learning focus: Authentication, authorization and RBAC Given: a known applicant and a documented policy When: the configured step or rule executes Then: compare actual data and routing with the expected outcome
Conceptual configuration plan, not an importable Pega rule. Labels and tools vary by release. Use the official mission environment to inspect current screens.
Try it yourself
Write one failed-authentication test and one authenticated-but-forbidden approval test. Explain why their expected outcomes differ.
Build a matrix of personas against create, view, assess and approve actions. Mark the minimum permissions. Explain how application access differs from permission to approve a particular case.
For this lesson, focus your notes on authentication, authorization and rbac. Record the inputs, configuration choice, observed result and one alternative that you rejected.
Common mistake
Knowledge check
What does successful authentication prove?
Check your understanding
It proves identity under the configured authentication method; it does not grant every application permission.
Go deeper with official resources
Pega Academy System Architect mission
Official ’25 certification objectives
