Custom Login Module, SSO Ticket validity & Login Module Stack

[Former Member]

Hi everybody,

we have a portal (running on jboss) which links to a J2EE web application (running on SAP WAS 6.40) which itself is protected by a custom login module and redirects to different WebDynpro applications (running on same WAS as the J2EE app) depending on some parameters.

So when we go from the portal to the J2EE web application, the custom login module authenticates the user, creates a MYSAPSSO2 Cookie and then redirects to a webdynpro app.

What happens is that the webdynpro app doesn't accept the cookie and redirects to the login mask.

Looking at the request header parameter HOST we have the request coming from sub1.sub2.mycompany.com, which is the portal.

The WAS is located on sub3.mycompany.com.

If we manipulate the HOST parameter to sub2.mycompany.com everything works fine and the webdynpro app successfully authenticates the user.

This does sound either like a domain relaxing issue or a multi domain issue, which we added as parameters to the CreateTicketLoginModule in the Login Module Stack for the J2EE web app.

Unfortunately without result.

Did anybody have a similar problem and can give some hints on how to solve this?

Any help is appreciated

Regards,

md

Edited by: Minh-Duc Truong on Jul 17, 2008 7:18 PM

Edited by: Minh-Duc Truong on Jul 17, 2008 7:19 PM

Edited by: Julius Bussche on Jul 18, 2008 7:25 PM

[Former Member]

Hi md,

I have split your 2nd question into a seperate thread => That would make them easier to answer as well, which will help.

You can find it here:

Cheers,

Julius

Edited by: Julius Bussche on Jul 18, 2008 7:26 PM