Hi everyone - revisiting an issue that I've been battling for a couple of years.
I'm wondering if anyone has TNEW shared session functionality working successfully for their TEST environment using the new (newest anyway) api method. (test-yoursite.tn.services/api/session)
I am able to get it working correctly on our Live side because the root domain for my custom application site is the same as for our Live TNEW site. (mycustomsite.mydomain.com and tickets.mydomain.com). I fetch a session from https://tickets.mydomain.com/api/session and when I redirect the browser over to our Live TNEW site it has the same session info already stored in the TNEW cookie and all the shared session functionality works great.
Not so good on the test side. I am able to fetch an encrypted message/session from our test TNEW api (fetch from https://test-mysite.tn.services/api/session) - this fetch is successful - I get a sessionkey from our Test database, but when I redirect the browser over to the TNEW test site it grabs a new session and stores it in the TNEWQA cookie. All the shared session functionality is lost.
I am guessing this fails because of cross-site restrictions on the cookie - can't create a cookie for .tn.services with a fetch request from mycustomsite.mydomain.com.
Noting the cross-site challenges and noting that we can no longer using a vanity CNAME (test-tickets.mydomain.com) for our TNEW test site - is it just impossible to do shared session for a test TNEW environment? Does anyone have this working?
Thanks in advance.
Cheers,
Bill WaughStarlight Theatre