Sure enough. I should have thought to try that.
[Expert@DallasSA]# mgmt_cli -f json -r true show object uid 6b647376-6f7a-4755-b3ca-adf3cc7d0b4e details-level full
{
"object" : {
"uid" : "6b647376-6f7a-4755-b3ca-adf3cc7d0b4e",
"name" : "P2L2 Section 1",
"type" : "access-section",
"domain" : {
"uid" : "41e821a0-3720-11e3-aa6e-0800200c9fde",
"name" : "SMC User",
"domain-type" : "domain"
},
"tags" : [ ],
"meta-info" : {
"lock" : "unlocked",
"validation-state" : "ok",
"last-modify-time" : {
"posix" : 1637433950042,
"iso-8601" : "2021-11-20T18:45+0000"
},
"last-modifier" : "WEB_API",
"creation-time" : {
"posix" : 1637433949870,
"iso-8601" : "2021-11-20T18:45+0000"
},
"creator" : "WEB_API"
},
"read-only" : false
}
}
Also interesting: access sections have an associated domain and can have tags. Extremely inconvenient to have to make a separate request per section just to see all that, though.
And it's a little weird that the 'show object' output doesn't include the rules in that section, or even any indication whether it has rules at all. Passing the access section's UUID to 'show access-rulebase' returns a generic error with no contents, which is interesting:
[Expert@DallasSA]# mgmt_cli -f json -r true show access-rulebase uid 6b647376-6f7a-4755-b3ca-adf3cc7d0b4e
{
"code" : "generic_error",
"message" : ""
}
[Expert@DallasSA]# mgmt_cli -f json -r true show access-rulebase uid 97aeb369-9aea-11d5-bd16-0090272ccb30 # This is the UUID for the object "Any"
{
"code" : "generic_error",
"message" : "Runtime error: com.checkpoint.objects.classes.dummy.CpmiAnyObject incompatible with com.checkpoint.objects.rulebase.RulebaseEntity"
}