Our application is built on PEGA 6.1 SP2. We are connecting to a REST service through Connect-HTTP to fetch employee information. We are using LDAP authentication to connect to this REST service. The service is now decommissioning LDAP and migrating to OAuth based authentication and authorization. Since OAuth is not supported in this version of PEGA, we may have to write custom logic within the PRPC application for the token generation, validation and access.
Could you please share some inputs on how this can be achieved? What rules need to be modified? Where the custom code needs to be written/handled? What logic needs to be implemented? How to override the default invokeaxis2 behavior only for this service?
***Edited by Moderator Marissa to update Support Case Details***