Question
Zensar Technologies Ltd
IN
Last activity: 31 May 2024 23:27 EDT
Node Level Data Page
Why it is mandatory to give Access group in Node Level data page?
***Edited by Moderator Marije to add Capability tags***
Accepted Solution
Updated: 31 May 2024 23:27 EDT
Eclatprime Digital Private Limited
AU
Hi @AbhishekC1725,
In Pega, specifying an access group for node-level data pages is mandatory due to several key reasons:
-
Security Context: The access group defines roles and permissions, ensuring the data page operates with the correct security context and has the necessary permissions to access and manipulate data.
-
Rule Resolution: It determines the ruleset context for rule resolution and execution, ensuring the correct rules are applied.
-
Performance Optimization: Access groups help optimize caching by ensuring only authorized data is cached and reducing unnecessary data fetches.
-
Consistency and Maintainability: Enforcing an access group standardizes configurations and simplifies auditing and monitoring, enhancing maintainability.
-
Best Practices and Governance: This practice aligns with security policies, preventing unauthorized access and ensuring compliance with organizational guidelines.
Overall, specifying an access group ensures security, proper rule resolution, performance optimization, and compliance with best practices in Pega applications.
Bits in Glass
IN
@AbhishekC1725 please check the below URL. Node level dpage is for meant for whole node level application that covers all the requestors. So as node level data page can't get a specific requestor access as it is not running on a particular requestor level, we explicitly provide access group for it's access.
NCS Pte. Ltd
SG
Hi @AbhishekC1725: Please check this and this.
Some additional ref:
https://support.pega.com/question/questions-about-node-level-data-pages
https://support.pega.com/question/how-node-level-data-page-behave-multinode-enviornment
Thanks.
Rulesstack Private Limited
IN
Hi @AbhishekC1725,
Thread, Requestor we need not specify any access group. But for the node level, we need to specify the same. Reason: Node level data page acts as a separate requestor that runs in its own execution stack, which is different from any requestor user.
Please go through the below link for your better understanding
https://support.pega.com/question/why-we-need-access-group-node-level-data-page
Thanks
Coforge DPA
IN
Node level dpage is for meant for whole node level application that covers all the requestors. So as node level data page can't get a specific requestor access as it is not running on a particular requestor level, we explicitly provide access group for it's access.
Accepted Solution
Updated: 31 May 2024 23:27 EDT
Eclatprime Digital Private Limited
AU
Hi @AbhishekC1725,
In Pega, specifying an access group for node-level data pages is mandatory due to several key reasons:
-
Security Context: The access group defines roles and permissions, ensuring the data page operates with the correct security context and has the necessary permissions to access and manipulate data.
-
Rule Resolution: It determines the ruleset context for rule resolution and execution, ensuring the correct rules are applied.
-
Performance Optimization: Access groups help optimize caching by ensuring only authorized data is cached and reducing unnecessary data fetches.
-
Consistency and Maintainability: Enforcing an access group standardizes configurations and simplifies auditing and monitoring, enhancing maintainability.
-
Best Practices and Governance: This practice aligns with security policies, preventing unauthorized access and ensuring compliance with organizational guidelines.
Overall, specifying an access group ensures security, proper rule resolution, performance optimization, and compliance with best practices in Pega applications.
Zensar Technologies Ltd
IN
@Koti Raja Thanks for response
Pegasystems Inc.
US
If your Question was resolved from @KotiR16754433 reply, please mark it as the Accepted Solution.