-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 10.0.0, 11.0.0
-
Component/s: authentication, session
-
Labels:
-
Support Ticket IDs:
If advanced server property 'com.iplanet.am.session.agentSessionIdleTime' is set to something other than 0 (i.e agent sessions will get timed out), OpenAM begins enforcing active session quotas on the agent users.
"2014-08-23 09:25:56" "Maximum Sessions Limit Reached.|module_instance|Application" id=WebAgent,ou=agent,dc=openam,dc=forgerock,dc=org "Not Available" 192.168.56.3 INFO dc=openam,dc=forgerock,dc=org "cn=dsameuser,ou=DSAME Users,dc=openam,dc=forgerock,dc=org" AUTHENTICATION-268 Application "Not Available" 192.168.56.3
To reproduce:
- Setup vanilla openam and agent install.
- Check normal operation, ensure agent uses more than 2 sessions.
- In OpenAM, set com.iplanet.am.session.agentSessionIdleTime to 120
- Reboot OpenAM
- Check normal operation, ensure agent uses more than 2 sessions.
- Enable Quota Constraints and change to DENY_ACCESS. Set maximum to 2 session (or 1).
- Observe agent begin to fail due to failed logins.
- is duplicated by
-
OPENAM-1682 Set session.setType(Session.USER_SESSION) for Agent/Application (when using agentSessionIdleTime)
-
- Resolved
-
-
OPENAM-6059 Agent sessions appear in console
-
- Resolved
-