Member since
07-29-2020
574
Posts
320
Kudos Received
175
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
305 | 12-20-2024 05:49 AM | |
353 | 12-19-2024 08:33 PM | |
351 | 12-19-2024 06:48 AM | |
292 | 12-17-2024 12:56 PM | |
284 | 12-16-2024 04:38 AM |
05-20-2022
06:44 AM
Hi Andre, Thanks again for taking the time and look into my access policy files. If you have noticed in the users.xml I have created an admin group with id "1966f436-0180-1000-ffff-ffffd1d17786" that the user "168b019c-0180-1000-ffff-fffffbf36c3a" is part of, this user group should have access to everything on the nifi canvas so Im assuming my user id implicitly will have access to everything as well, is that correct? even with that I went and give access to my user id explicitly to the target processor group with permission to view, modify and operate component, but still getting the 403 error! Keep in mind when I call the same API using nifi InovkeHttp providing the same access token it only works when I provide SSL Context Service that points to the same truststore & keystore files used to secure the nifi instance, could that be the problem in postman since I did not provide the SSL context there even though Im using https in the url? Im not sure how this can be configured in postman. Thanks for your help.
... View more
05-19-2022
06:40 PM
I sent you both the users and authorizations xml content in private message. Thanks!
... View more
05-19-2022
02:58 PM
Hi Andre, I sent you the authorizers content in private message. thanks for your help
... View more
05-19-2022
01:10 PM
Hi Andre, Not sure what do you mean by "enabled Ranger for authorization"? Can you please elaborate? Also the user Im getting the access token for is the same user that can log in to nifi and have all kind of permissions added to view\modify any workflow. Not sure what else I could be missing. Thanks
... View more
05-18-2022
04:30 PM
Thanks Andre, I did manage to get the token using access/token api. however when I provided the token in postman as Bearer authentication I still get the 403 Forbidden response. Here is my request and response info as captured by Fiddler, let me know if you see anything wrong: PUT https://[server name]:9443/nifi-api/processors/385fcdc0-0180-1000-0000-000030a768e3/run-status HTTP/1.1 Content-Type: application/json Accept: application/json, text/javascript, */*; q=0.01 Keep-Alive: timeout=100, max=50000 Authorization: Bearer [access token] User-Agent: PostmanRuntime/7.29.0 Postman-Token: 5900c41a-f704-43f3-a2e4-a425eeb22569 Host: [host name]:9443 Accept-Encoding: gzip, deflate, br Connection: keep-alive Content-Length: 215 { "revision": { "clientId": "8F3BD748-DBCC-4703-8743-1D98A24B95C2", "version": 1.16, "lastModifier": "user.name" }, "state": "RUNNING", "disconnectedNodeAcknowledged": true } Response: HTTP/1.1 403 Forbidden X-Frame-Options: SAMEORIGIN Content-Security-Policy: frame-ancestors 'self' X-XSS-Protection: 1; mode=block X-Content-Type-Options: nosniff Strict-Transport-Security: max-age=31540000 Content-Length: 0 Server: Jetty(9.4.45.v20220203)
... View more
05-18-2022
09:04 AM
Hi, I have a secured Nifi cluster. Im trying to call a nifi api to start\stop processor using postman. I followed the instruction for the api "PUT /processors/{id}/run-status". Provided the Bearer token and the Json Body. However I keep getting 403 Forbidden message. Does anybody know why? I'm able to run other APIs successfully such as getting processor info "GET /processors/{id}"! Im guessing its because Im using SSL secured nifi with jks keystore and truststore, but not sure how to provide this information to postman. Can anyone help please?
... View more
Labels:
- Labels:
-
Apache NiFi
05-12-2022
01:31 PM
1 Kudo
I never worked with Hive DB, but if it only takes avro format and you have csv you can use processor ConvertRecrod to convert a record from one format to another. In this processor you create CSV Reader service and the writer is Avro
... View more
05-10-2022
01:15 PM
1 Kudo
There is a lot of articles\videos around learning Regular Expression. The one I provided using what is called positive lookbehind (?<=), which means: find the Id which contain alphanumeric characters with hyphen (-) that is proceeded (lookbehind) with the text "requestUid"
... View more
05-10-2022
12:31 PM
1 Kudo
Not sure if this is the the most efficient way, but you can use ExtractText by creating new attribute with the following regular expression: (?<=\"requestUid\":\s")[A-Z-a-z-0-9\-]+ Not sure if you can accomplish that using evaluatejsonPath processor, but given that the path can be different its probably hard to accomplish
... View more
05-10-2022
12:28 PM
there are a lot of processors that can help you with that for example : PUTSQL, PutDatabaseRecord, ExecuteSQL
... View more