Minor bug showing a particular domain

[Bob_Zimmerman]

Found what appears to be a minor bug showing the full properties of an object which comes with Check Point management servers' default configurations. This is on R82 jumbo 12:

[Expert@DallasSC]# mgmt_cli -f json -r true -d "System Data" show object uid "41e821a0-3720-11e3-aa6e-0800200c9fde"
{
  "object" : {
    "uid" : "41e821a0-3720-11e3-aa6e-0800200c9fde",
    "name" : "SMC User",
    "type" : "domain",
    "domain" : {
      "uid" : "a0eebc99-afed-4ef8-bb6d-fedfedfedfed",
      "name" : "System Data",
      "domain-type" : "mds"
    },
    "icon" : "Objects/domain",
    "color" : "black"
  }
}

[Expert@DallasSC]# !! details-level full
mgmt_cli -f json -r true -d "System Data" show object uid "41e821a0-3720-11e3-aa6e-0800200c9fde" details-level full
{
  "code" : "generic_err_object_not_found",
  "message" : "Requested object [41e821a0-3720-11e3-aa6e-0800200c9fde] not found"
}

 I only noticed it when I was trying to fetch a bunch of predefined objects so I can prepopulate documents. Definitely no impact at this point.

[PhoneBoy]

As you probably know, the generic object APIs aren’t officially supported.
Not sure it’d be considered a bug 😉

[Bob_Zimmerman]

I'm only calling 'show object'. There's no "generic" anywhere there except in the error returned when I run 'show object ... details-level full'.

[Amir_Senn]

It seems to me that this might happen for specific objects that doesn't support full-details.

This "SMC User" object is kind of unique.

Can you see if this happens to you on other objects as well?

[Bob_Zimmerman · Accepted solution]

Oops. Turns out I noticed this almost a year ago and was told it's expected behavior.

[Daniel_Kuhl1]

That's what I thought in first place after reading your post: it's expected for objects like this, but I really was not 100% sure without validating it myself or asking someone who knows it. 😁

[Bob_Zimmerman]

It still seems like the error message should be better. Telling me it can't find the object is ridiculous. The same API call with one less parameter found it.

[Daniel_Kuhl1]

Indeed the error message could be better and should be more specific. After checking the available error messages, it seems that it's the most closest or most accurate. It should be telling you that there are no full details available for this object or something like this.