Installation Guides › Implementation Guide › Implementation Overview › SOA Security Manager Overview › SOA Security Manager Architecture and Components › Data Stores › Session Store

Session Store

(Optional) When SOA Security Manager authenticates a user, the Policy Server issues a session ticket. A session ticket contains basic information about the user and authentication information for the user. By default, SOA Security Manager implements session management through non–persistent sessions. If non–persistent sessions are enabled, an Agent writes the session ticket to a cookie on the browser of the users. However, some SOA Security Manager features require persistent sessions.

If persistent sessions are enabled, an Agent must write the session ticket to a stand–alone database.

You deploy a SOA Security Manager session store (session store) for the following primary reasons:

• If a SOA Security Manager log off URI is implemented, a session store prevents a SOA Security Manager session from being used again after a user logs off.
• To provide support for features that require persistent user sessions.

Agents use this information to identify users and provide session information to the Policy Server.

Note: For more information about configuring a session store, see the documentation roadmap.

More information:

SOA Security Manager Documentation