Introducing Sessions

A session in AM is a token that represents a usually interactive exchange of information between AM and a user or identity.

AM creates an authentication session to track the user’s authentication progress through an authentication chain or tree. Once the user has authenticated, AM creates a session to manage the user’s or entity’s access to resources.

Sessions require the user or client to be able to hold on to cookies. Cookies provided by AM’s Session are a reference to where the session is stored; the CTS token store. By default, the cookie’s name is iPlanetDirectoryPro. You will see this name across the documentation, but your environment will use a different cookie name,

AM session-related services are stateless unless otherwise indicated; they do not hold any session information local to the AM instances. Instead, they store session information either in the CTS token store. This architecture allows you to scale your AM infrastructure horizontally since any server in the deployment can satisfy any session’s request.