I am inheriting an application with SFDC mashup via code generator. SFDC Extender is not being used. Currently, 2 capabilities are required - to create a case wherein member details from SFDC are sent to PRPC to auto-populate, and to be able to search for existing cases.
Currently, these are built out as 2 different links in SFDC. So if a user creates a case (with member details sent) and later wants to search for an existing case, 2 different sessions are created in PRPC. This is causing performance issues.
Question is - is there a way via SFDC Extender or standard mashup to SSO the user into PRPC from SFDC on login (so that user can access search from PRPC dashboard), and still allow the user to trigger case creation from SFDC to autopop the member data? Of course, without creating a second session.
***Edited by Moderator Marissa to update platform capability tags****
For my testing with SFDC I have multiple gadgets each defined in it's own visual force page and associated with a tab. Once I load one tab the second mashup always use the same session in PRPC. How did you get it to use different sessions? Are they both using the same PRPC end point? I will double check later.
We use SESSION cookies that are in memory at the browser level so not sure how you would get two seperate sessions when you load one mashup then load a secondary one.
I use SSO for my mashups but using just the /IAC servlet and IACAuthentication AuthService. You can use a SAML AUthService for a mashup. These just control access to PRPC but once the session is established it should be using the same session. You have to make sure the each of the mashups uses a different thread name so they don't overwrite content.