We've run into an issue with a Teamraiser straddling Wordpress and LO. The question is: is there a way to defer to existing JSESSIONIDs and not receive new JSESSIONID cookies when making API calls? Could this potentially be solved by including xhrFields: {withCredentials: true } in the calls?
The general walkthrough of the issues is below (platform in square brackets):
- [LO] Participant visits site, logs in, is given JSESSIONID A
- [LO] Participant clicks link to visit one of the event pages in WordPress
- [WP] API calls made on page load
- CRConsAPI call made
- Purpose is to verify and persist user session information from LO on WP
- Methods called are LoginTest
- The API call request passes JSESSIONID A
- CRTeamraiserAPI call made
- Purpose is to populate leaderboards
- Methods called are getParticipants, getTeamsByInfo, getCompaniesByInfo
- The API Call request does not pass JSESSIONID A
- The response passes back a new JSESSIONID B, which now exists alongside JSESSION A in the user's cookies ?
- [WP] Participant clicks to return to their Participant Center 2 [LO]
- [LO] The participant center doesn't fully load, instead freezing mid loading bar and giving an auth error on an API call in the console. Specifically, JSESSIONID B is scoped by Path to '/CRConsAPI' so it is passed alongside JSESSIONID A in the GetUser method call (as part of the PC3 loading), and breaks the auth match. If JSESSIONID B cookie is deleted and page refreshed then the PC will load.
Note: API Calls are made using luminate extend 1.7.1