Member since
11-23-2022
12
Posts
1
Kudos Received
2
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
344 | 07-01-2025 06:50 AM | |
1364 | 10-25-2023 05:35 AM |
10-20-2025
06:28 AM
Hello I'm trying to use Nifi Hashi Corp Vault Parameter Provider with Kubernetes authentication. - Nifi versions is 2.4.0 - Hashi Corp version is 1.19.5 From my Nifi pod I get to authenticate successfully using the following curl curl -s -k -X POST -H 'X-Vault-Namespace: DATA/DATAOPE/EC002I002621/' -H 'X-Vault-Request: true' -d '{"jwt": "<content of file /var/run/secrets/kubernetes.io/serviceaccount/token>", "role": "role_k8s_auth_demo_re_ns002i007839"}' https://hvault.staging.my_company/v1/auth/kubernetes_demo_re_ns002i007839/login From the pod I then get to make a successful secret retrieval with the follwing curl curl -H "X-Vault-Request: true" -H "X-Vault-Namespace: DATA/DATAOPE/EC002I002621/" -H "X-Vault-Token: <token retrieved by previous command>" https://hvault.staging.my_company/v1/secret/data/test I try to make sense of the doc and cannot get to a working configuration I setup my HashiCorp Vault Client with the following properties direct properties vault.kubernetes.kubernetes-path kubernetes_demo_re_ns002i007839 vault.kubernetes.role role_k8s_auth_demo_re_ns002i007839 vault.namespace DATA/DATAOPE/EC002I002621/ and set up the SSL context service appropriately. I set up my Parameter Provider with the following direct properties key value path : DATA/DATAOPE/EC002I002621/secret/ version : kv 2 secret name pattern : .* I get the following error message : Error fetching parameters for ParameterProvider[id=xxxx]: Cannot login using Kubernetes: permission denied Can someone help me sort out what I'm doing wrong ? Is there a way to dump the API calls made by the Parameter Provider ? Regards. Regards
... View more
Labels:
- Labels:
-
Apache NiFi
07-01-2025
06:50 AM
Fixed by using toolkit 1.28.1 to access nifi 1.27.x
... View more
04-25-2025
06:45 AM
Thanks for the reminder regarding the semantic of merge-param-context. I overlooked the contents of the help and my initial posting. Regards
... View more
01-31-2025
04:29 AM
Based on the initial input in the question, slightly adapted the following seems to work for me (1.27.0) docker run --rm --name nifi -p 8080:8080 \ -e NIFI_WEB_HTTP_PORT=8080 \ -e NIFI_WEB_HTTPS_PORT= \ -e NIFI_WEB_HTTPS_HOST= \ -e NIFI_SECURITY_KEYSTORE= \ -e NIFI_SECURITY_KEYSTOREPASSWD= \ -e NIFI_SECURITY_KEYPASSWD= \ -e NIFI_SECURITY_TRUSTSTORE= \ -e NIFI_SECURITY_TRUSTSTOREPASSWD= \ apache/nifi:1.27.0 --- --- from container nifi@xxxxxxxxxxxx:/opt/nifi/nifi-toolkit-current/bin$ ./cli.sh _ ___ _ Apache (_) .' ..](_) , _ .--. __ _| |_ __ )\ [ `.-. | [ |'-| |-'[ | / \ | | | | | | | | | | ' ' [___||__][___][___] [___]', ,' `' CLI v1.27.0 Type 'help' to see a list of available commands, use tab to auto-complete. Session loaded from /home/nifi/.nifi-cli.config #> nifi get-root-id xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
... View more
01-09-2025
03:09 AM
ZK 3.8.4 uses the LogBack feature for logging, which uses 2 libraries logback-core-1.2.13.jar logback-classic-1.2.13.jar ( Missing Jar ) one of them was missing from my bundle. I downloaded and copied the jar in zookeeper/lib/ dir and restarted the service. This worked for me. Steps - Locate the logback jar, download the other missing jar, and paste in that dir. cd /opt/ wget https://repo1.maven.org/maven2/ch/qos/logback/logback-classic/1.2.13/logback-classic-1.2.13.jar cksum logback-classic-1.2.13.jar | grep -i "103870831 232073" chown root:root logback-classic-1.2.13.jar cp logback-classic-1.2.13.jar /usr/odp/3.3.6.0-1/zookeeper/lib/ cp logback-classic-1.2.13.jar /usr/odp/3.3.6.0-1/cruise-control3/dependant-libs/
... View more
10-25-2023
05:35 AM
The problem seemed to be caused by wrong access policies on PG under the root. With the wrong credentials the name attribute of certain PG was not returned in the response which caused pg-list to fail. Adding read policy for the credentials on the PGs solved the case. ?! Regards
... View more