RE: Sametime server's browser problem + javaconnect.cab Victor Toal 7.Nov.08 08:47 PM a Web browser Lotus Domino Extended Products Portlets 7.0Windows
Did you follow the steps on how to implement SSO from the docuemntation? It is VERY explicit.
The reason why it does not work could be many:
-The SSO token is not created with the same domain name
-You did not create the SSO token in WebSphere and then import it into Domino correctly
-While importing the SSO token/creating the Domino Web SSO document you did not have your Domino client's location document set to a server in the domain you are creating the SSO document in
-You called the SSO token in the Web SSO document something else than[ Ltpa Token] (default name)
etc., etc., etc. ...
A few tests to do:
Does SSO work from Domino to Portal?
Does SSO work between multiple Domino servers?
Does SSO work between multiple WebSphere servers (if you have any)
Also - any specific reason why you are using Sametime 7.0? It is rather old now and actually has quite a few bugs that were fixed in subsequent releases.