Cloudera Community
MattWho
user rank
user rank
Master Mentor

Re: Nifi-Registry OIDC

by New Contributor in Support Questions
‎12-03-2024 02:39 AM
1 Kudo
‎12-03-2024 02:39 AM
1 Kudo
It works fine @archie ! Thanks! This is my following snipped docker-compose code: nifi-registry: image: apache/nifi-registry:1.23.2 container_name: nifi-registry hostname: nifi-registry restart: "no" ports: - 18443:18443 volumes: - ./nifi/certs/localhost:/opt/certs environment: TZ: America/Sao_Paulo NIFI_REGISTRY_WEB_HTTPS_PORT: 18443 AUTH: oidc KEYSTORE_PATH: /opt/certs/keystore.jks KEYSTORE_TYPE: JKS KEYSTORE_PASSWORD: changeit TRUSTSTORE_PATH: /opt/certs/truststore.jks TRUSTSTORE_PASSWORD: changeit TRUSTSTORE_TYPE: JKS INITIAL_ADMIN_IDENTITY: test@test.com NIFI_REGISTRY_SECURITY_USER_OIDC_DISCOVERY_URL: http://<LOCAL_KEYCLOAK_IP>:8080/realms/TEST/.well-known/openid-configuration NIFI_REGISTRY_SECURITY_USER_OIDC_CONNECT_TIMEOUT: 10000 NIFI_REGISTRY_SECURITY_USER_OIDC_READ_TIMEOUT: 10000 NIFI_REGISTRY_SECURITY_USER_OIDC_CLIENT_ID: nifi NIFI_REGISTRY_SECURITY_USER_OIDC_CLIENT_SECRET: <CLIENT_SECRET> NIFI_REGISTRY_SECURITY_USER_OIDC_PREFERRED_JWSALGORITHM: RS256 NIFI_REGISTRY_SECURITY_USER_OIDC_ADDITIONAL_SCOPES: openid,email,profile NIFI_REGISTRY_SECURITY_USER_OIDC_CLAIM_IDENTIFYING_USER: preferred_username networks: - test-net     ... View more

Re: how to stop and start processor-group in NIFI ...

by Community Manager Community Manager in Support Questions
‎11-29-2024 06:18 AM
‎11-29-2024 06:18 AM
@pankajgaikwad As this is an older post, you would have a better chance of receiving a resolution by starting a new thread. This will also be an opportunity to provide details specific to your environment that could aid others in assisting you with a more accurate answer to your question. You can link this thread as a reference in your new post. Thanks. ... View more

Re: Nifi : Implement Sleep Mechanism in nifi witho...

by Contributor in Support Questions
‎11-27-2024 09:58 PM
‎11-27-2024 09:58 PM
Thank you @MattWho . Yes , Initially, i have designed the partial failure. Now , i have changed the design to captured on the failure flow files and send the alert on that. Thank you.  ... View more

Re: Restart Nifi nodes without data loss

by Explorer in Support Questions
‎11-27-2024 11:22 AM
‎11-27-2024 11:22 AM
Running the restart shell script inside container did it for me! Thanks for the help @MattWho! ... View more

Re: No available buckets after secure Nifi connect...

by Master Mentor Master Mentor in Support Questions
‎11-22-2024 05:25 AM
1 Kudo
‎11-22-2024 05:25 AM
1 Kudo
@Armel316  Since you only have two user group providers (ldap and file), that means that both are returning user "xxx".  If the ldap-user-group-provider is returning user "xxx" you don't want to define that same user through the file-user-group-provider.    What this means is that the users.xml file that the file-user-group-provider is loading users from on startup contains user "xxx".    The file-user-group-provider will ONLY generate a users.xml file if one does not already exist.  If one already exist the file-user-group-provider will NOT make any modifications to an existing users.xml if you modify the provider configuration.  Once a users.xml file exists, the expectation is that all future user/group modification happen via the UI. NOTE: The users.xml does not contain any users or group being loaded by other providers in to NiFi memory. So you have two options here: Rename the current users.xml file so a new one is created on startup with only the 3 defined node-identities.  (this is preferred method) Manually modify the users.xml to remove all users that are being synced by the ldap-user-group-provider. Please help our community thrive. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt ... View more

Re: Access failed after apache nifi installation

by New Contributor in Support Questions
‎11-21-2024 08:40 AM
‎11-21-2024 08:40 AM
For remote access to login page, just add to c:/windows/system32/drivers/etc/hosts your server IP and hostname same on linux, /etc/hosts   ... View more

Re: Replace ConsumeASB Processor with the InvokeHt...

by Community Manager Community Manager in Support Questions
‎11-20-2024 11:28 PM
1 Kudo
‎11-20-2024 11:28 PM
1 Kudo
@s198, Did the response assist in resolving your query? If it did, kindly mark the relevant reply as the solution, as it will aid others in locating the answer more easily in the future. However, if you still have concerns, please provide the information that @MattWho  has requested. ... View more

Re: Can't enable cluster option for NIFI container

by New Contributor in Support Questions
‎11-19-2024 09:01 PM
‎11-19-2024 09:01 PM
Thank you for your reply. I just tried deploying a NiFi container without modifying the start.sh script, and I found that when I set NIFI_CLUSTER_IS_NODE to true, the container still gets stuck and then stops. I find this strange—if the container doesn’t support clustering, why does the official image allow this environment variable to be set? I think this is misleading. I noticed that version 2.0.0 supports setting nifi.cluster.leader.election.implementation to KubernetesLeaderElectionManager. Does this require NiFi to be deployed at the same level as Kubernetes, or does NiFi need to be deployed as a pod within Kubernetes? I look forward to your response. Thank you! ... View more

Re: Nifi not starting because of OnScheduled()

by Master Mentor Master Mentor in Support Questions
‎11-19-2024 10:30 AM
1 Kudo
‎11-19-2024 10:30 AM
1 Kudo
@phadkev  Would need to see more of the nifi-app.log to better understand what is going on here. Are you seeing the same org.apache.nifi.controller.StandardProcessorNode Timed out while waiting for OnScheduled exception for other components or just this executeScript processor? The exception itself is generic and could be thrown for any processor class. Are you ever seeing the log line telling you the NiFi UI is available at the following urls? If so NiFi is up. Are you seeing NiFi shut back down with some exception and stack trace in the nifi-app.log. What you shared implies NiFi is having issues scheduling this specific processor to execute.  This could very well be caused by an issue with the custom script that was build and used in this processor. If you NiFi is really not coming up, you could modify the nifi.properties file by changing  "nifi.flowcontroller.autoResumeState=true" to "nifi.flowcontroller.autoResumeState=false".  This will allow you NiFi to start without starting any processors.  You could then search the UI for the ExecuteScript component processor with id "acb441ba-c36b-1fdd-53f2-3a4821d43833".    Disable it and start all your other processors.  Restart your NiFi to see if you still have any issues.   This isolates the issue to this processor and your script. Please help our community grow. If you found any of the suggestions/solutions provided helped you with solving your issue or answering your question, please take a moment to login and click "Accept as Solution" on one or more of them that helped. Thank you, Matt   ... View more

Re: NiFi for file movement

by Contributor in Support Questions
‎11-15-2024 09:10 AM
1 Kudo
‎11-15-2024 09:10 AM
1 Kudo
@MattWho Thanks for your reply 👍 ... View more
Contact Me
Community Statistics
Member Since ‎07-30-2019 10:41 AM
Last Visited
Posts 3,123
Kudos received 1559