Setting up different AuthPolicies for each implementation application.
We have a framwork layer followed by multiple implementation for each clients based on the country. Ex: For a client, We have seperate implementation layer for USA and Canada.
In such a scenario, how can we define different AuthPolicies for each Implementation layer. The OOTB AuthPolicies (Data-Admin-System-AuthPolicies) generates a single instance with name 'AUTHENTICATIONPOLICIES' which in turn used in the load activity of OOTB node level Datapage 'Declare_AuthPolicies'. Also few of the OOTB activities use the hardcoded value 'AUTHENTICATIONPOLICIES' in Obj-Open step.
In our scenario, Users from a client having access to both the Application ( USA and Canda ) need to have different AuthPolicies set and managed.
Is it recommended to extended this OOTB behaviour by creating different Authpolicies per implementation application?.
Does PEGA has any recommendation?
***Edited by Moderator Marissa to update platform capability tags****