Close popover
Robin Markose (markr1)
Principal Solutions Engineer
Pegasystems Inc.
markr1 Member since 2014 2 posts
Posted: September 29, 2016
Last activity: October 6, 2016

Customization in Authentication

Requirement : Assume there are two application in a PRPC installations. Each application needs it's own customized version of authentication activities. Is this scenario possible in PRPC?
Description: Assume there is only one PRPC installation with system name as "pega". There are two applications in that installation AppA (with WebLDAP1 authentication service) and AppB(with WebLDAP2 authentication Service).
AppA ruleset contains AuthenticationLDAP1 activity which is configured in WebLDAP1. AppB ruleset contains AuthenticationLDAP2 activity which is configured in WebLDAP2.
But there is only one requester type "pega.BROWSER" where we can configure only one unauthenticated accessgroup which either points to AppA or AppB at a time.
So if AppA:Unauthenticated accessgroup is selected , it will find AuthenticationLDAP1 activity when PRWebLDAP1 url is used, but will not take AuthenticationLDAP2 activity when PRWebLDAP2 is used and vice versa.
In short, i am not able to configure the instance to make both the applications use  it's own custom authentication activities  at the same time. 


Low-Code App Development Security
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.