FortiManager
FortiManager supports network operations use cases for centralized management, best practices compliance, and workflow automation to provide better protection against breaches.
HatiUjja
Staff
Staff
Article Id 338335
Description This article describes what to do when an Adom lock is stuck.
Scope FortiManager.
Solution

This article helps in removing a lock that is stuck.

 

To remove the ADOM lock, check the admin session list on the FortiManager and identify the session of the user who has locked the ADOM. Verify the details by running the below command.

 

diagnose system admin-session list

 

The example below demonstrates how the output of the above command will display.

 

FMG# diagnose system admin-session list


*** entry 0 ***
session_id: 458 (seq: 0)           <--- Session id to be used.
username: admin
admin template: admin
from: GUI(10.0.0.1) (type 1)
profile: Super_User
adom: root
session length: 19 (seconds)
idle: 5 (seconds)

 

*** entry 1 ***
session_id: 48085 (seq: 1)
username: admin
admin template: admin
from: jsconsole(10.0.0.1) (type 0)
profile: Super_User
adom: root
session length: 10 (seconds)

 

Use the session ID of the user who has locked the ADOM and kill that admin session by running the below command.

 

diagnose sys admin-session kill <session ID>

 

Note: Verify the details before performing this command as this can impact the legitimate session of another admin if not done carefully.