How to back out Single sign out configuration

[Former Member]

Hello,

I began to configure Single Sign On, but had a lot of trouble so backed out what I had done. Now when I go into the UME in the portal, I get a login screen, which remains there despite what userid and password I put in there.

When I look at the default trace log I see the following (read from bottom upwards):

No authenticated user found.

Received no SAPLogonTicket. Authentication stack: [ticket].

got [ume.configuration.active]: [true]

got [ume.configuration.active]: [true]

redirecting to /logon/logonServlet?redirectURL=%2Fwebdynpro%2Fdispatcher....

Redirect: /logon/logonServlet?redirectURL=%2Fwebdynpro%2Fdispatcher....

No authenticated user found.

Received no SAPLogonTicket. Authentication stack: [ticket].

got [ume.configuration.active]: [true]

got [ume.configuration.active]: [true]

This tells me that, somewhere in java there is still some SSO config linguring.

Where do I look and how do I completely back this out?

Thanks

Stuart

[Former Member]

Hi,

It looks like you changed the ticket login module stack (aka policy configuration).

Go to visual admin->security provider and select ticket from the list.

The default setup I think is

1. EvaluateTicketLoginModule Sufficient

2. BasicPasswordLoginModule Required

3. CreateTicketLoginModule Optional

Cheers

Dagfinn

[Former Member]

Dagfinn,

Thanks for coming back so quickly.

Unfortunately that did not work, I still get exactly the same errors.

Further back in the log a see a further 'warning':

no authscheme found that has auth template sap.com/con.sap.lcr*sld.

Thanks

Stuart

[Former Member]

Actually, on closer inspection of the trace file, the errors are produced when using J2EE_GUEST.

Thanks