I am trying to test a Pega Web mashup code using the PRWebLDAP1 servlet. When i try to load the mashup using the normal prweb servlet , the interaction portal with the interaction case works fine i.e. I am able to click around and create cases. However when I am using the ldap servlet and authenticating a new user , the portal is displayed along with the interaction case, but I am not able to create any cases from the interaction driver. The AddTask button is not responding to the clicks.Can you please point me where I am going wrong? Here is the code snippet:
From a mashup perspective you have this configured correctly. You are using "createNewWork" and providing the class and the flow name correctly.
With the LDAP authentication in the mix are you logging in with a user that has the correct permissions? When you test with "/prweb/PRServlet" are you using the SalesUser as well or your own developer ID?
the user with the LDAP authentication has the same privilege as the other user (sales@myBank) which I am using via the standard Servlet. Actually the LDAP user mimics the profile of this user during login and hence have the same access rights.
Are there any specific configurations required on the UI rules as well? we are using CSFS application and the interaction work object needs to be shown in the mashup with the composite view.
I do know I can replicate similar behavior when trying to load a full end user portal with a mashup using a mashup action of "display" and harness class and name parameters. The menu options don't work etc. The portal requires initialization to run properly so we use a mashup action of "openWorkByURL" and query parameter using "pyActivity=ShowDesktop" to solve that.
I wonder if we are running into something similar here and calling the flow to run just isn't enough. There is missing initialization done when launching a new interaction from the end user portal that's missing when running just this flow in a mashup.
However, you have this working with /prweb/PRServlet. Do you get a login screen when you test this way? And just type in your developer login/password and then the mashup content displays after login?
I second your opinion with the display of the portal in the mashup. But here the problem is intermittent as it happens with the LDAP login and not with the normal user. When I use the standard servlet, I pass in the parameters as shown above to the mashup div. In the backend I assume the gadgetmanager js file is using the preparing the doUIAction activity with the complete url and sends in the encoded query string with user name and password. Hence I dont get the login screen but directly go into the interaction case. So this is a bit puzzling since the same set of actions is also being used when I refer the LDAP url. But somehow the initialization i not happening as you have mentioned.
Moreover I would assume that in the real scenario the authentication of the user would happen in the host application and it would pass on the user credentials (in a secured way I guess :) ) to the mashup. So can we directly use the standard servlet here?? Is there any sample where you have seen custom authentication applied to mashups?
That is also a bit of a challenge as I see. I am testing it from a sample html on my local machine. The requestors are getting created but not passivated in SMA. I am not sure if there is any other way to test this. we are using 7.2.2 for all the applications