Tuning OpenAm maximum session number could be very important for performance issues, not well documented, so we will intend to share with you in this article how we manage it.
1) OpenAM Maximum session Number
OpenAM maximum session Number is described by the attribute
- Default value is 5000. Specify the maximum number of allowable concurrent sessions.Login sends a Maximum Sessions error if the maximum concurrent sessions value exceeds this number.
2) Accessing to this attribute using the Admin Console
Using openAM UI, it is possible to access to this attribute as follows:
- Configuration -> Server and Sites -> Default Server Settings -> Session-> Session Limits
(Property ‘Maximum Sessions’)
3)Max Session Stastistics
It is possible to follow the Cache Session statistics, which are provided each minute located at:
Following the values of MaxSession in the amMasterSessionTableStats indicates you if run out of sessions.
In this case, you need to increase the value of com.iplanet.am.session.maxSessions
4) Important consideration
Bear in mind that sessions are stored in JVM memory. If you increase your session maximum number, you also need to increase your JVM heapspace as well.
Specialised in IAM (security, access control, identity management) and Open Source integration, settled in 2004 by IAM industry veteran, JANUA offers high value-added products and services to businesses and governements with a concern for Identity Management and Open Source components.
JANUA provides better security, build relationships, and enable new cloud, mobile, and IoT offerings from any device or connected thing.
Les derniers articles par Olivier Rivat (tout voir)
- Howto Docker with Keycloak – examples - 16 mai 2018
- Migrating from ODSEE to OpenDJ-WrenDS - 30 avril 2018
- OpenID: understanding JWTand signed JWT usage with RedHat SSO Keycloak - 25 avril 2018