Messaging Server supports user ID/password authentication, client certificate authentication, and Access Manager. There are some differences, however, in how the protocols handle network connections between client and server.
When a POP, IMAP, or SMTP client logs in to Messaging Server, a connection is made and a session is established. The connection lasts for the duration of the session; that is, from login to logout. When establishing a new connection, the client must reauthenticate to the server.
When an HTTP client logs in to Messaging Server, the server provides a unique session ID to the client. The client uses the session ID to establish multiple connections during a session. The HTTP client need not reauthenticate for each connection; the client need only reauthenticate if the session is dropped and the client wants to establish a new session. (If an HTTP session remains idle for a specified time period, the server will automatically drop the HTTP session and the client is logged out; the default time period is 2 hours.)
The following techniques are used to improve the security of HTTP sessions:
The session IDs are bound to a specific IP address.
Each session ID has a timeout value associated with it; if the session ID is not used for a specified time period, the session ID becomes invalid.
The server keeps a database of all open session IDs, so a client cannot forge an ID.
The session ID is stored in the URL, but not in any cookie files.
For information about specifying configuration parameters for improved connection performance, see Chapter 5, Configuring POP, IMAP, and HTTP Services
For information on Access Manager see Chapter 6, Enabling Single Sign-On (SSO)