Okta Access Gateway CLI Session Times Out After Five Minutes in Version 2024.9.2
Last Updated:
Overview
Okta Access Gateway (OAG) version 2024.9.2 terminates the Command Line Interface (CLI) session after five minutes due to a security-enforced idle timeout on the management account. Resolve this by executing a script from the shell to temporarily increase the session timeout limit.
The session closes after five minutes, even while active, when accessing the shell through the management console. A slow connection during an upgrade also causes a timeout issue.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Okta Access Gateway (OAG)
- Version 2024.9.2
Cause
Okta Access Gateway enforces a five-minute idle session timeout for security reasons. Accessing a local shell from the management console uses a different account than the oag-mgmt account. The oag-mgmt account remains idle, causing the Command Line Interface (CLI) session to exit after five minutes. A slow connection from the appliance to the repository server during an upgrade causes similar behavior.
Solution
How is the session timeout limit increased for the Okta Access Gateway shell?
Execute the session timeout script from the shell to increase the limit to fifteen minutes, and revert the setting to the default value after completing the activity.
NOTE: For security reasons, only change the session timer for the duration of the activity and revert it upon completion. Contact Okta Support if the upgrade times out after setting the timer to fifteen minutes.
- Access the shell from the management console.
- Execute the following command to change the session timeout to fifteen minutes.
sudo /opt/oag/scripts/mgmt/setSessionTimeout.sh 900- Complete the required activity.
- Execute the following command to revert the timeout settings to the default value.
sudo /opt/oag/scripts/mgmt/setSessionTimeout.sh 300
