autolock

[jdprovine]

It was recommended that we turn on autolock so that people would not step on each other commits so we did. We had a non admin user create a filter, it requites a commit and he has no admin rights to commit. So the firewall became locked and no one could commit the change - anyone run into this before? If you have how did you deal with it. We have since turned off autolock.

[Kaje]

your admins should be able to click on the lock, on the top right, and either take the lock of the user, or remove the lock entirely. 

We had a user that was not allowed by company policy to commit changes, she would build everything, then have other admins review and handle the commit. 

[BPry]

@jdprovine,

A superuser can remove any other user's admin lock. This can be done either through the GUI by clicking on the lock, selecting the Lock that you would like to remove, and clicking on the 'Remove Lock' option.

You can alternatively run the following within the CLI to remove the commit lock. 

request commit-lock remove admin bpry

Or you can remove it through the API like so.

https://IP-Address/api/?type=op&cmd=<request><commit-lock><remove><admin>bpry</admin></remove></commit-lock></request>&key=KEY

[jdprovine]

@BPry

Yeah I thought I would just be able to commit the config change because I am a superuser but why would autolock case and non admin user to create a lock? I will give your suggestion a try. Weird as it may seem I was able to do the OS upgrade and at the end it commited everything thats how I got through it

[reaper · Accepted solution]

how to remove admin lock

[jdprovine]

@reaper

that is awesome thanks