This article describes how to resolve an invalid protocol number when retrieving a Service Object from FortiGate registered with FortiManager using JSON API.
FortiManager responds to an invalid protocol number when retrieving service objects using JSON API as below:
The Protocol numbers for each service are as follows:
However, the reason why the protocol number included in the code returned by FortiManager is different is that this value is not a protocol number in FortiManabger, but an internal mapping of option enum to an integer.
FortiManager has the internal mapping of an option enum to an integer: