Betsy Terrell 20.Aug.08 11:21 AM a Web browser Installation2.0Windows
I have an existing Portal 6.0x environment with SSO working between WAS and Domino environments. I have a separate Lotus Connections install. I deployed the Lotus Connections portlet to my portal. Everything is in the same DNS domain. Seeing strange things with SSO.
1. I take the LTPA key generated in the Portal environment and import it to Connections environment following the proper steps. I did not generate a key on the Connections side and import it into the Portal side as nowhere can I see this as a requirement.
2. I log into portal and go to the Connections page, where my portlet is deployed. I see content in the portlet ie- I am not prompted to re-authentenicate here.
3. When I select a piece of content, a blog for example, I am taken to Connections (in my case in-place although the default is a new window that pop's up). I see the "Log In" in the upper right hand corner, so it does not know who I am.
4. When I select the tab "My Blog" I am prompted to log in so SSO is not working, at least not completly.
When I look at the LTPA tokens, I see that that they do not match up, ie- one has the default realms created when Connections was configured and the other has the host name of the ldap server. So they are different. So, in order to get these two enviroments working together after the fact, what has to change on what side?
Return to top
SSO between Portal (WAS 6.0x) and L... (Betsy Terrell 20.Aug.08)
. . 
Print this page
