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.
PEG
IN
I don't think PRPC do support this kind of implementation. At presnt we can use one authentication scheme for all applications in a PRPC system.
Let's wait for other folks on this community to share their thoughts.
Cognizant Technology Solutions
US
Hi Markr,
As per my Knowledge, The way you are looking for the approach,Pega Out of Box wont Support this.
FYI, UNauthenticated access group should be one at organizational level(we should not be creating multiple).and with one unauthenticated we can configure multiple Custom Servlet URL's (same approach i have implemtned for one of my client with Custo mServlet,it worked application switch).
Why cant you Consider this approach, Let user login with One LDAP Custom URL ad authenticate( since For Organization authentication will be one), while use switches to the application from pega we can call second LDAP authorization rules and set the profile?.