Question

10
Replies
3670
Views
BoiT6888 Member since 2015 1 post
FDIC
Posted: March 8, 2016
Last activity: April 6, 2016
Closed
Solved

Custom Authentication

Hi,

We installed Pega 7.1.9. We would to configure custom authentication with Oracle Access Manager as Service Provider per paragraph below (this is from the authentication overview of Pega e-learning). Is there anyone familiar with this process/configuration can help us? We plan to move Pega to QA and production soon. High level steps would be nice as well.

Thanks

BB

Web Access Management

Let’s look at a typical Web Access Management implementation with PRPC sing CA SiteMinder. The same general mechanism applies to all off‐the‐shelf Web Access Management solutions.

1. User Requests a protected resource – For example:

http://www.mycorp.com/PRExtAuthServlet

2. Web Agent examines request and queries Policy Server to determine if PRExtAuthServlet is a protected resource. If so, Web Agent checks wether or not the user has been authenticated.

3. If they have not been, the user is presented with the login form.

4. The Policy Server passes the credentials to LDAP directory for authentication.

5. If successful the Web Agent writes an encrypted cookie onto the user’s browser, which will identify the user to the web agent for subsequent requests.

6. The Web Agent then queries the Policy Server to determine authorizations for the requested resource.

7. The policies mandate that to access /PRExtAuthServlet/* the user must belong to the group PRPC_User or PRPC_WorkMgr (hypothetical)

8. The Policy Server queries the directory to determine if the user is in one of the appropriate groups

9. If so, the web agent caches the authorization and allows the request to pass through to the reverse proxy, appending customized http header variables containing the user ID, group name and other information about the user. The Reverse Proxy routes the request to the appropriate application server.

10. The PRPC application generates the page and responds to the request.

11. If needed, the PRPC application polls the LDAP Directory for additional user information

 

Low-Code App Development Installation and Deployment Security
Moderation Team has archived post
Share this page LinkedIn