@Olwe
How is zabbix authenticating it self with your NiFi? When NiFi is secured, all clients must be authenticated and authorized. An HTTP 401 means the client was not authorized.
NiFi does not use sessions. So when a user logs in via a username and password, if the authentication was successful, a bearer token is issued for the user for that specific NiFi node. That bearer token will remain valid for the duration configured in your NiFi login provider or until the logout endpoint is invoked. The client is expected to include that bearer token in all subsequent requests. If you hit a NiFi rest-api endpoint like .../nifi-api/flow/cluster/summary without a bearer token or a client certificate, the client will be treated as "anonymous" and not authorized. You should see this unauthorized endpoint request logged in the nifi-user.log. When you access rest-api endpoints via the browser which you used to login, the browser takes care of including the bearer token. I am not familiar with Zabbix, but same requirements exist (get bearer token and include bearer token in future rest-api calls)
For example, obtaining a token using a login provider:
curl 'https://<nifi-hostname>:<nifi-port>/nifi-api/access/token' \
--data-raw 'username=<username>&password=<password>' \
--compressed \
--insecure
Above will return the <bearer token>.
Then you would use that bearer token in your future rest-api requests:
curl 'https://<nifi-hostname>:<nifi-port>/nifi-api/flow/cluster/summary' \
-H 'Authorization: Bearer <bearer token>' \
--compressed \
--insecure
If you found that the provided solution(s) assisted you with your query, please take a moment to login and click Accept as Solution below each response that helped.
Thank you,
Matt
