Netscape's support for single sign-on currently doesn't include the user's SMTP password, network password, OS password, database passwords, Kerberos passwords, and so on. For information about third-party solutions that extend single sign-on to these kinds of resources, see Netscape Security Partners.
Proxy Server
Proxy Server 2.5 supports SSL tunneling, which means that an SSL connection can be established between a client and a server via the Proxy Server. If the Proxy Server is not configured for client authentication, this will happen transparently between a client and a server that both support single sign-on as described in this guide. If the Proxy Server is configured for authentication via name and password, the user will have to type in a separate password before being allowed to access the server.
Although the standard configuration for Proxy Server 2.5 doesn't support client authentication with certificates, it is possible to configure the server as a reverse proxy (web server stand-in), in which case the Unix version does support client-based authentication to Proxy Server 2.5. Future versions of Proxy Server will fully support certificate-based client authentication and single sign-on.
Directory Server
Directory Server 1.x doesn't support single sign-on for users who are using the directory to look up information. These versions of the Directory Server do support looking up a user's certificate in the directory entry for the user on behalf of other servers that support single sign-on. This is shown as step 5 in Figure 3.
Directory Server 3.x will fully support single sign-on.
Catalog/Compass Server
Catalog Server 1.0 doesn't support single sign-on. Future versions, which will be known as Compass Server, will fully support it.
Calendar Server
Calendar Server 1.0 doesn't support single sign-on. A future version will support it.
Last Updated: 10/20/97 14:15:48
Any sample code included above is provided for your use on an "AS IS" basis, under the Netscape License Agreement - Terms of Use