We have a mobile application that uses the SAP .Net Connector 3.0 to call Function Modules. The .Net Connector uses the MYSAPSS02 cookie that we extract from our SAP Portal site after doing an HTTP POST request passing the username and password to establish a session.
So there are a few recurring issues with this logic that we are trying to overcome. First is the null response we often receive from Portal. The code POST’s the request, and looks for the MYSAPSS02 cookie in the response and very frequently the cookie is not found in the response. We have yet to find a sound rhyme or reason as to why the response comes back null. When checking the J2EE logs all we got was "Reason=[Authentication did not succeed.]#". Definitely was not a password issue because the .Net connector throws a completely different error if the wrong credentials are passed.
The other issue is that quite often, the SSO cookie sent in a response, that we store gets rejected by the backend. Throwing an error to the effect of “the system is unable to interpret the SSO ticket received” which results in the loss of the current session forcing our users to have to re-authenticate.
So far this issue has gone unresolved and as the application user base grows, it has put more strain on the logic. Just a few other areas of note, the application itself is hosted on a Windows Server 2008. It does ultimately reside at the same sub domain level as our Portal Server(i.e. myportal.domain.com & mobileapps.domain.com). After initially testing whether it was a routing issue, we pointed our application to 1 specific backend server, and 1 specific portal server and the result made no positive impact. Hopefully someone can help shed some light on what may be causing this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.