MYSAPSSO2 ticket is not created
Hi, We are using a Siteminder logon module to accomplish Single Sign on to the Enterprise Portal. 7.04. SSO Logon is successful to the portal, but the MYSAPOSS2 ticket is not created. Hence we can not get automatic sign on from EP to the next abap system.
Is there actual documentation for the CreateTicketLoginModule? And how it acts in a Logon Stack? For example: if there are two authentication modules (such as Siteminder and Basic) would either one being true cause it to Create a ticket if create ticket is last? Or would one immediately proceeding it being false, cause it not to be created?
We did have 5 logon modules as defined in Header Variables Logon Stack documentation (Evaluate, Siteminder, Createticket, Basic, CreateTicket), but wondered if the last "create ticket" might be wiping out the one from the prior one, ,even though it never presented a Basic Login screen when Siteminder was successful. Now we just have one CreateTicketLoginModule at the end (Evaluate, Basic, Siteminder, Createticket) , and have the same behavior. It always creates a ticket when doing the BasicPassword logon (to NWA), but not when the Siteminder SSO is successful to the EP.
Any other suggestions of why the MYSAPOSS2 ticket might not be created?
Ruth Jones replied
Update for everyone, it turned out the cookie issue was due to differences in the domains (hidden under the covers) in the front end reverse proxy, alias to the SAP servers, server names, etc.
Once we used some different URL's and network teams modified some names.. it is working.