- Use a product such as TAM/WebSEAL, which can be tricky to implement but the cool thing is that it not only allows SSO between web applications, it can also be used for SSO between the desktop and Lotus Connections.
- Develop a custom Trust Association Interceptor (TAI) for WebSphere. This minimizes the cost, but requires a Java Developer to know WebSphere's TAI API in order to do this. If you haven't heard of,or don't know what TAI is, it's awesome!!! It's really "easy" to use. The disadvantage is that it only works if one web application links to another and can pass the username of the current user as part of the URL or in the HTTP headers.
- Use TAM eSSO, a client-based utility which stores passwords. The problem with this is that it's not really SSO. Users will still be prompted for a username/password, but it will be automatically entered by this utility that must be installed into each user's PC.
We are currently going to pursue #2 and see how far we can get. We are a little bit strapped for hours, so we may not be able to finish this, and as I said before, I need to figure out whether Sharepoint can create URLs to Connections and embed the username in the links.