Sorry typo on my part. Even with the */api/v1/admin/topics it works.   I cloned the nifi github repo and added some more log statements to the executeStreamProcessor changed the edited the logback.xml to enable DEBUG for that processor. It looks like it stripping the quotes in payload.   Here is an example request: curl -X POST -H 'Content-Type:application/json' -d '{"name": "Apple AirPods", "data": {"color": "white", "generation": "3rd", "price": 135}}' https://api.restful-api.dev/objects   This works in the command line.   If you configure the executeStreamCommand like this: Command Arguments Strategy: Command Arguments Property Command Arguments: -X POST -H 'Content-Type:application/json' -d '{\"name\":\"Apple AirPods\",\"data\":{\"color\":\"white\",\"generation\":\"3rd\",\"price\":135}}' https://api.restful-api.dev/objects Command Path: curl Argument Delimiter: " " (Space)   Here's what I see in the logs -  Executing and waiting for command: curl, with the arguments: [-X, POST, -H, 'Content-Type:application/json', -d, '{\name\:\Apple AirPods\,\data\:{\color\:\white\,\generation\:\3rd\,\price\:135}}', https://api.restful-api.dev/objects]   @cotopaul , @ckumar , @MattWho , @steven-matison - Is there a way to get around this? ... View more

@cotopaul  The reason why I say that is because if I change the command arguments to this -  -X GET -H referer:${Referer} -H 'Content-Type: application/json' --negotiate -u : -b /tmp/cookiejar.txt -c /tmp/cookiejar.txt http://SMM-HOSTNAME:8585/api/v1/admin/brokers   It returns successfully. The only that changed is the HTTP Request Method and removing the Payload.  ... View more

@cotopaul  I have verified that the same command works from the command line. I think the executeStreamCommand must be doing some sort of formatting prior to sending the request to the Streams Message Manager Server.    A GET request works using the ExecuteStreamCommand because there is no payload.  I can't use the invokeHTTP because it currently doesn't have configuration to authenticate using kerberos which is why I fell back on using ExecuteStreamCommand.    ... View more

Switching to a new version of NiFi solved the problem. ... View more

@MattWho  We have two separate CDP clusters set up. One cluster is our administration cluster (ie source of truth) that houses things like all of our NiFi Flows in the NiFi Registry. We want the other cluster or clusters to get access to these flows from their NiFi environments.  However, the only way to get access to that administration NiFi Registry externally is through Knox.    Right now I set up all the topologies and authentication/authorization needed to do so but on restart of NiFi it strips the URL path in the Registry Client for Knox endpoint which I have to manually add back each time. ... View more

Can anyone help with this? I am using NiFi v1.16. ... View more