- CheckMates
- :
- Products
- :
- Developers
- :
- API / CLI Discussion
- :
- Re: not able to set session timeout with mgmt_cli
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
Are you a member of CheckMates?
×- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
not able to set session timeout with mgmt_cli
I can't seem to set a longer then default session timeout using management cli at the moment. For example, if i wanted to increase it to 1200 second over the default 600 seconds i am using the command
mgmt_cli --root true login session-name test-session-timeout session-description test-session-timeout session-timeout 1200 --format json
But after logging in if i run a show session using the returned session id - session timeout still shows as 600seconds. Has anyone else experienced this? i also tried with mgmt_cli --conn-timeout, same result
mgmt_cli --session-id $SID show session
uid: "819cd746-8cd7-4263-bc9b-773ee0a56f65"
name: "test-session-timeout"
type: "session"
domain:
uid: "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxxxxxx"
name: "System Data"
domain-type: "mds"
state: "open"
user-name: "WEB_API"
description: "test-session-timeout"
last-login-time:
posix: 1564636139402
iso-8601: "2019-08-01T06:08+0100"
expired-session: false
application: "WEB_API"
changes: 0
in-work: true
ip-address: "127.0.0.1"
locks: 0
email: ""
phone-number: ""
connection-mode: "read write"
session-timeout: 600
comments: ""
color: "black"
icon: "Objects/worksession"
tags: []
meta-info:
lock: "unlocked"
validation-state: "ok"
last-modify-time:
posix: 1564636140597
iso-8601: "2019-08-01T06:09+0100"
last-modifier: "WEB_API"
creation-time:
posix: 1564636139796
iso-8601: "2019-08-01T06:08+0100"
creator: "WEB_API"
read-only: true
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hey Richard,
I have also experienced this in the past. My guess is that it's related to bug which occurs when somebody is using the "--root true" parameter. If you do not specify this part and instead log in "manually" with a user who has the required set of permissions it is working as expected. Once you want to use the root user - w/o further login steps - the session-timeout defaults to 600. If you still want to use the the root argument you could add the "keepalive" command after a while in order to not let the session time out.
Regards,
Maik
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank Maik you are correct it works with a username and password. I see the session timeout is set correctly then.
I was actually testing with a certificate user and password rather then -r true using the mgmt_cli -c -p option - it would appear that this mechanism is also blighted by the same bug:( and does not set the session time out to the given length.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hm, maybe @Robert_Decker can help us in this case? 🙂
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I've just made it a habit to issue "unset TMOUT" when I first log into a CLI.
My fingers remember it down even though my brain doesn't always remember.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
What version are you trying this with?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Support ticket the way to go here.
