The PRWebLDAP1 Servlet is mapped to a PRCustom style AuthService and that is the best approach for what you are doing.
Do you display the login screen in your authentication activity? This is probably the same Servlet users use to access the system for standard usage so I would think so. If you see a PRPC style login screen right after clicking the link then the answer is yes. When you test with just PRServlet is the prompt for authentication in the form of a Basic Authentication popup?
When the user hits submit authentication will be completed here and this URL in the form, because it contains no pyActivity or pyStream parameter, will default to showing the users home portal as defined in their AccessGroup.
Thanks for the explanation. Yes when PRServlet is used regular HTTP pop up appears in the screen but no login screen. Once user put the user id and password it redirects him to WO bypassing . But in PRWebLDAP1 it doesn't show the popup instead it shows the login screen. If user logs in it shows the default dashboard.
With PRCustom style authentication the login activity will be passed a pyQueryString parameter from the engine level. What we need to do here is make sure the pyQueryString is appended properly, when present, to the Login screen HTML form action attribute when displayed.
Okay, time for the solution. (I tested this in 7.1.7 but it will work in 7.1.5)
Couple of things you need to know before you start this:
1) What Login Screen are you using
In your login activity you should see a step like this.
This will load the challenge stream defined in your AuthService in the custom tab in the "Credential Challenge Stream".
If blank, like above, it's using Web-Login. (You are probably using Web-Login or a customized version of it as it's always expected it will be modified for application/company branding)
2) The ruleset, available to unauthenticated users, you can make changes in.
You need to have a ruleset available to users before they are authenticated to save changes into.
You probably have this setup already. Check your Data-Admin-Requestor <SystemName>.Browser instance,, SysAdmin->Requestor Type, and make sure it contains an AccessGroup that provides access to a ruleset used for SSO customizations. This is the AccessGroup used prior to authentication, not the AccessGroup the user will use once authenticated.
So this AccessGroup is references a product called SSOAuth that has one ruleset SSOAuth. (I don't give unauthenticated users access to a full application)
1) Copy Web-Login or your current Login HTML if you have already have something custom. (If you have upgraded from a older PRPC version you may want to start with Web-Login)
Thanks for your quick response. We have implemented in the same way but the problem is it works PRServlet but not PRWebLDAP servlet . After the user is authenticated through LDAP service the system is not redirecting to the assignment ,instead it shows the default dashboard.
I suggest you wait until after the experience of applying Chris's instructions to actual customer system, after which you publish the refined document according to what adjustments were needed to make it work on the customer's system. /Eric