1. We have tried to use the "verify" REST API call and according to the documentation it suppose to verify the candidate configuration on the Panorama. Every time we have tried to use this call, it performed a commit on the Panorama (enqueued a commit job), but we expected it will enqueque a validate job. The relevant REST API is: https://hostname /api/?type=commit&cmd=<commit><validate></validate></commit> Is there another flag we need to use? do we use the REST API call in a wrong way? Is this a Panorama bug? 2. Using the REST API we have discovered some bugs that we would like to report: 2.1. When adding via REST API a rule that already exists with the same name, the new rule's data is being appended to the existing rule (the source, destination etc. of the new rule is added to the existing one in the existing rule). We believe that the expected behavior should be to return an error that this rule already exists. 2.2. It's possible to create 2 different address objects or service objects with the same name but with different types (netmask, range etc...) via the REST API. Again, we believe that the expected behavior is to return an error that an object with this name already exists.
... View more