I was just trying to query the jsonrpc api of Zabbix when i found something i cannot wrap my head around.
Zabbix implements the JSON-RPC 2.0 specification (according to https://www.zabbix.com/documentation...authentication), but after getting a token with method 'user.login' you are expected to supply this token on subsequent requests as an 'auth' key within the request.
But according to the specification (https://www.jsonrpc.org/specification), the request object consists of only the following keys:
* jsonrpc
* method
* params
* id
This is a problem when trying to use for example the go jsonrpc client because it does not allow to add arbitrary keys to the request.
Also, i found no documentation stating that the token can be provided via other ways (like in the header of the request).
Am i missing something?
Zabbix implements the JSON-RPC 2.0 specification (according to https://www.zabbix.com/documentation...authentication), but after getting a token with method 'user.login' you are expected to supply this token on subsequent requests as an 'auth' key within the request.
But according to the specification (https://www.jsonrpc.org/specification), the request object consists of only the following keys:
* jsonrpc
* method
* params
* id
This is a problem when trying to use for example the go jsonrpc client because it does not allow to add arbitrary keys to the request.
Also, i found no documentation stating that the token can be provided via other ways (like in the header of the request).
Am i missing something?