![Close [x]](http://dw1.s81c.com/i/c.gif){kind=small}
This paper explains the steps to configure single sign-on (SSO) for IBM Lotus® Sametime® Community Server, Meeting Server, Proxy Server, Media Manager, and the Connect client, using Simple and Protected GSSAPI Negotiation Mechanism (SPNEGO) with the Lotus Sametime System Console as the authentication server. SPNEGO enables the SSO mechanism for Microsoft® Windows® clients that are part of a Microsoft Active Directory® Domain.
- Overview
- Configuring SPNEGO on Active Directory Server
- Configuring SPNEGO for Sametime System Console
- Enabling SSO for WebSphere Application Server
- Enabling the Snoop servlet in WebSphere Application Server
- Creating a unique Security Domain for the System Console
- Configuring client machine browsers
- Enabling SSO on Sametime Meeting Server
- Enabling SSO on Lotus Proxy Server
- Enabling SSO on Lotus Media Manager (AV)
- Enabling Sametime Connect Client with SPNEGO
- Troubleshooting and testing
- Conclusion
- Resources
- About the authors
| Description | Name | Size | Download method |
|---|---|---|---|
| White paper in PDF format | IntegratingSPNEGO_SametimeUpdated.pdf | 1,880 KB | HTTP |
Information about download methods Get Adobe® Reader®
- Participate in the discussion forum.
-
Sametime wiki article, "Setting up a full IBM Lotus Sametime 8.5.1 environment using the Sametime system console."
-
developerWorks Lotus Sametime product page.
-
Lotus Sametime product documentation.
-
IBM Redbooks® publication, "Lotus Sametime Application Development Guide."
-
developerWorks WebSphere Application Server zone.
Conall O'Cofaigh is a Software Engineer working on the Sametime Verification Test team. He's been with IBM since 2008, focusing on integration and interoperability across Lotus Sametime products.
