thanks for the reply, I have this document with me but We are trying a different approach to setup LDAP in Weblogic and connect it through PRServletContainerAuth. Do you have any idea regarding this approach.?
You're probably getting a basic authentication popup because of the WebLogic HTTP authentication issue related to default settings in the WebLogic config.xml. The following steps are taken from our PRPC install document for WebLogic:
If you don't have this set to "false" you will get a basic authentication popup.
How PRServletContainerAuth and LDAP Configuration are linked?
They are not linked. You have setup container managed authentication at the WebLogic server level. Regardless of how you have configured this, LDAP or other, users have to be authenticated before they are allowed to access the application running in the container, in this case PRPC.
Does PRServletContainerAuth look for a kerberos ticket?
Nope. Our side of the Container Managed Authentication is very easy as the engine layer simply calls the Data-Admin-Operator-ID.EstablishOperator activity to log the user into PRPC passing the User Principal provided by the container as a parameter to the activity. There is no authentication/validation on our side, just mapping the User Principal provided by container to a PRPC Operator record and logging the user into PRPC.