08-25-05 01:54 AM
If you've logged into WebSphere Portal (assuming you have configured
WebSphere Portal to use Domino Ldap correctly) and have to log into Domino
application again, this means SSO doesn't work. In this case, you will have
two different values for the LtpaToken, and this can be caused by many
different reasons. Make sure your Domino server document allow
Multi-Session authentication and that you import the generated key from
WebSphere Application Server into Domino properly. Also, both WebSphere
Application Server and Domino server must use the same Ldap server.
If SSO works, you only have to log into either Domino or WebSphere Portal.
In this case the LtpaToken should be exactly the same.
Look for an IBM Redbook called Domino and WebSphere Together (I used the
second edition and it should give you all the ideas to use for WebSphere
Application Server 5 and Domino 6.x).
LTH.
"dhirenjoshi" <dhirenjoshi.1uaixa@mail.webservertalk.com> wrote in message
news:dhirenjoshi.1uaixa@mail.webservertalk.com...
>
> I captured the LTpaToken cookie value for two instances.
>
> 1. One when I login into the portal server only
> 2. When I login into the Domino only.
>
> Both the cookie values are different.
> Should they be different values. ?
> I would assume for SSO they need to be the exact same value.
> If they are different what could posibly be the reason that they are
> different ?
>
>
> Appreciate any suggestions.
>
>
> Thanks
> Dhiren
>
>
>
> --
> dhirenjoshi
> ------------------------------------------------------------------------
> Posted via http://www.webservertalk.com
> ------------------------------------------------------------------------
> View this thread: http://www.webservertalk.com/message1177114.html
>
[ Post a follow-up to this message ]
|