Previous Contents Index Next |
iPlanet Portal Server Reference Guide |
Chapter 7 Single Signon
Single Signon Overview
The Single Signon provides developers of iPlanet Portal Server API's a mechanism to let users access the applications freely after the initial session signon, rather than prompting for authentication information to access each application during that session. The session/user authentication is established at initial signon by the session server.At a high-level, single signon application development requires developers to:
Special Cases
HTTP Basic Authentication is automatically handled by the gateway. It monitors user logins, then writes the URL and encrypted authentication information to the Profile Server.Similar to HTTP Basic Authentication is NetFile. NetFile notes what's been used (username, password, mount information) and remembers it for next time.
A system administrator can also pre populate URLs in the Profile database.
Before logging into the Portal Server the servlet program will print out the value of the session ID.
Note The cookie name would normally be retrieved by the application from the http header.
Instructions for using Single Signon
This section provides information for linking a Single Signon authorization to a user's iPlanet Portal Server desktop.
Command Line Example
iPlanet Portal Server software must be installed to use this sample.
Set IPS_BASE to the iPlanet Portal Server installation directory.
cd $IPS_BASE/SUNWips/sample/sso. then type make.
Copy the class files to the appropriate directory under:
Modify the web server configuration.
- $IPS_BASE/SUNWips/lib
- on the portal server, e.g., the SSO.class would be copied to:
- $IPS_BASE/SUNWips/lib/com/iplanet/portalserver/sso
Add the following line to the web server servlets.properties file:
- The web server configuration files are in the directory:
- $IPS_BASE/netscape/server4/https-servername/config
- where servername is the FQDN of the portal server.
Add the following line to the web server rules.properties file:
- servlet.sso.code=com.iplanet.portalserver.sso.SSO
- Replace the package and servlet names with the names chosen for this SSO servlet
Restart the portal server:
- /sso=sso
Test the servlet by logging in to Portal Server and entering the following URL:
https://gateway/http://server:8080/sso
Include the iPlanet Portal Server Classes
At a minimum, the Java client application should import the iPlanet Portal Server Profile, Logging, and Session classes, as shown here.
Single signon checks to see if the session is valid by looking for the cookie (planted by the Session) with the name iPlanetPortalServer.
Previous Contents Index Next
Copyright © 2000 Sun Microsystems, Inc. Some preexisting portions Copyright © 2000 Netscape Communications Corp. All rights reserved.
Last Updated May 04, 2000