AnsweredAssumed Answered

decodeSSOToken failing through SDK API. SMSESSION cookie has custom name.

Question asked by MJC1206 on Apr 23, 2014
Latest reply on Jul 31, 2014 by MJC1206

We are currently troubleshooting an issue with a new setup including R12 using the SDK API to connect to remote policy servers. The Agent is able to successfully connect to the policy server but decodeSSOToken is failing (unable to decode). One of the differences in the R12 setup is that the authentication provider has changed the name of the SMSESSION cookie, i.e. ABCSESSION. We are wondering if this is causing the failure. Does anyone have any experience with a similar setup?