InfoCenter Home > 4.4.1.1.3: Securing sessionsHTTP sessions and security can be integrated in IBM WebSphere Application Server. When security integration is enabled in Session Manager and a session is accessed in a protected resource, every resource from then on must be secured. You cannot mix secured and unsecured resources. Security integration in Session Manager is not supported in form-based log-in unless LPTA is used. Security integration rules for HTTP sessions
Programmatic details and scenariosIBM WebSphere Application Server maintains the security of individual sessions. An identity or user name, readable by the com.ibm.websphere.servlet.session.IBMSession interface, is associated with a session. An unauthenticated identity is denoted by the user name "anonymous." IBM WebSphere Application Server includes the com.ibm.websphere.servlet.session.UnauthorizedSessionRequestException interface, which is used when a session is requested without the necessary credentials. The Session Manager uses the WebSphere security infrastructure to determine the authenticated identity associated with a client HTTP request that either retrieves or creates a session. WebSphere security determines identity using certificates, LPTA, and other methods. After obtaining the identity of the current request, the Session Manager determines whether the session requested using a getSession() call should be returned. The table lists possible scenarios in which security integration is enabled whose outcomes depend on whether the HTTP request was authenticated and whether a valid session ID and user name was passed to the Session Manager.
* com.ibm.websphere.servlet.session.UnauthorizedSessionRequestException is thrown to the servlet. |
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|