Forum Discussion
APM SSO re-authenticates after Inactivity timeout 900 seconds.
Hi,
As the APM use the same session ID for both applications, if you change the variable session.inactivity_timeout, it is the same behavior as changing the Access profile inactivity timeout.
Since inactivity timeout is reached, the session is deleted from APM session table... If you want to allow SSO for 24H, you must configure inactivity timeout as 24H.
If you use LTM+APM profiles, users limit is not APM CCU license but Access Session license which is a limit of the appliance model and not upgradable with an addon license (except 7000 and 10000 appliances)...
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
