Field level ACL removes sys_id

[kmlutz]

For security requirements, we need to limit what fields are provided access based upon an ID. Once the ACLs are created, the sys_id of the "tables" are no longer available. The ACLs are being setup for an ID performing a direct call to SN. It has hard-coded in it's logic to be able to use the sys_id field and not another field that may have the same data. I know there may be other ways to do it but we are trying to use their integration tool for the work which seems designed to use sys_id throughout its logic.

Anyone know if there is a way to limit access to a table like cmdb_ci_win_server via ACLs and yet be able to provide the sys_id?

Thanks.

[Slava Savitsky · Accepted solution]

Not sure if it is going to give the desired effect and solve your issue but you could give it a try... Although sys_id is not available for selection in the dropdown list on the form, you could edit the name of your ACL from the list. There you should be able to enter cmdb_ci_win_server.sys_id

[kmlutz]

Slava,

You are a genius (and perhaps devious which I like as well)!

I was able to pick another field, create the ACL and then edit it via the list view to be sys_id.

I will adjust several of the classes we are using to try a test but I think this may work!

Thank you.