where-used command needs more than read-only all privileges ?

[Gongya_Yu]

I like to use where-used the command, but the my API  account only has read-only privilege. I read to know publish is removed from version 81.

Can I use it with read-only all privilege ?

thanks !!

[Tomer_Noy · Accepted solution]

Looks like this was a bug that was introduced in one of the JHF takes. The latest R81.20 JHF (that was released as ongoing today) has a solution for this issue.

More info is available in: https://support.checkpoint.com/results/sk/sk181471

[Gongya_Yu]

thanks so much!  

On our 81.20, I got the following with the read-only all account

[Expert@sms-uwt:0]# mgmt_cli where-used name hunt
Username: xxxxxx
Password:  **********
code: "generic_error"
message: "Null Pointer exception: null"

This is definitely some bug.  

But It works on 81.20 vmware.

80.20 has the following for the read-only all account

code: "err_normalization_failed"

message: "Work session was not found. Please verify that you are not in the read-only session mode"

Discarding the changes.

Discard failed, the following error has occurred:

code: "err_normalization_failed"

message: "Work session was not found. Please verify that you are not in the read-only session mode"

[Christian_Koehl]

You can also use this as a workaround. Please note, this will give write permissions to objects.

[Gongya_Yu]

thanks !!  We already reported this to Checkpoint. We noticed hotfix 26 broke this.