Member since
07-29-2020
558
Posts
307
Kudos Received
167
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
112 | 11-28-2024 06:07 AM | |
77 | 11-25-2024 09:21 AM | |
213 | 11-22-2024 03:12 AM | |
116 | 11-20-2024 09:03 AM | |
313 | 10-29-2024 03:05 AM |
01-25-2021
10:26 AM
OK, Its unfortunate that I did not get any help from the support community about this but the good news after several trials and many hours I was able to resolve it and Im sharing my experience to help those who might get stuck in the future regarding the same issue: 1- No need to set up any of the TLS properties if you are connecting to LDAP:// url and not LDAPS://. You can comment or remove this part. 3- Authentication Strategy: SIMPLE 2- Manager DN: if you are using windows open Active Directory Administrative Center (can be installed ). Do global search for one of the accounts you are familiar with and going to use, once located right click to select properties, scroll down to Extensions section and click Attribute Editor tab, locate the distinguishedName attribute and that will be the value to use in the Manager DN. It will be something like : CN=lastName.FirstName,OU=Standard Users,OU=Users,OU=LocationOU,OU=OrgName,OU=SomeOU,OU=AnotherOU,DC=DomainName,DC=com 3- Manager Password: the selected account password from above. 4-Url: The Ldap url, example : LDAP://ldap.DomainName.com/ 5- User Search Base: Use the Same string from Step 2 without the the account CN, Example: OU=Standard Users,OU=Users,OU=Location,OU=OrgName,OU=SomeOU,OU=AnotherOU,DC=DomainName,DC=com 6- User Search Filter: This is what you will use to add user and login to nifi. What worked for me is the "sAMAccountName={0}" which you can find set under the Attribute Editor (step 2) and it refers to search by the user name (example: lastname.firstname). 7- Identity Strategy: USE_USERNAME 8- Make sure to add the provider name (Example: ldap-provider) to nifi.properties. 9- Restart nifi. 10- using the default admin account created when setting up secure TLS on the installation server (Example: my_username) to add the AD user to Users and Set the Policies using user name from above. 11- From another machine launch nifi from the browser and you should be prompted to log in. Login using the same account credential you added to nifi and you should be in. Other helpful information can be found: https://pierrevillard.com/2017/01/24/integration-of-nifi-with-ldap/comment-page-1/ good luck.
... View more
12-12-2020
07:42 AM
Can someone help please. Im trying to run a test pilot for to see if Nifi can be adapted as tool of choice. The tool is impressive in terms of capabilities and out of the box components but It cant be used if its not easily integrated with our environment. I tried calling support on the phone and left a message, contacted sales via email but no response. One of the factor we have to adapt a tool is the ease of getting support when needed and so far the coulder community is not showing that unless Im doing something wrong.
... View more
12-09-2020
08:10 AM
Hi Im having trouble configuring the ldap to work with Nifi. First I was able to secure my nifi instance following the instruction under : "https://nifi.apache.org/docs/nifi-docs/html/walkthroughs.html#securing-nifi-with-tls" When I access Nifi and select the certificate I can see the account CN=my_username, OU=Nifi top right. Next step was to setup Ldap and for that I followed this link "https://pierrevillard.com/2017/01/24/integration-of-nifi-with-ldap/comment-page-1/" . In my login-identity-providers.xml file the ldap-provider was configured as the following (I used #### for sensitive info): <provider> <identifier>ldap-provider</identifier> <class>org.apache.nifi.ldap.LdapProvider</class> <property name="Authentication Strategy">SIMPLE</property> <property name="Manager DN"></property> <property name="Manager Password"></property> <property name="TLS - Keystore">./conf/keystore.jks</property> <property name="TLS - Keystore Password">####</property> <property name="TLS - Keystore Type">jks</property> <property name="TLS - Truststore">./conf/truststore.jks</property> <property name="TLS - Truststore Password">###</property> <property name="TLS - Truststore Type">jks</property> <property name="TLS - Client Auth"></property> <property name="TLS - Protocol">TLSv1.2</property> <property name="TLS - Shutdown Gracefully"></property> <property name="Referral Strategy">FOLLOW</property> <property name="Connect Timeout">10 secs</property> <property name="Read Timeout">10 secs</property> <property name="Url">LDAP://ldap.####.com</property> <property name="User Search Base">OU=Standard Users,OU=Users,OU=US-Houston,OU=####,OU=Engineering,OU=Divisions,DC=####,DC=com</property> <property name="User Search Filter">sAMAccountName={0}</property> <property name="Identity Strategy">USE_USERNAME</property> <property name="Authentication Expiration">12 hours</property> </provider> However when I go back to Nifi and select Users I dont see anything added there from the ldap server except for the main user added while securing nifi. The log file doesnt show any error. What am I doing wrong? Can you help please.
... View more
Labels:
- Labels:
-
Apache NiFi
08-07-2020
10:31 AM
Hi, Im trying to utilize the rety relation of the PutSQL processor by redirecting it to the RetryFlowFile processor. However nothing seem to trigger this relationship. My understanding is that the retry is triggered when the DB could not be reached such as bad connection string, sql server is down...etc. but no matter what I do on the sql server to test this scenario, the retry is not triggered, instead an an exception is thrown (jdbc.SQLServerException) and the flowfile is pushed back to the queue and penalized! Here is what I did on my sql server express instance to test: - Disable the SQL Server service. - Changing the connection string in the JDBC connection pool service to be incorrect. - Taking the Database instance offline - Even blocking the target table by doing select inside transaction with wait time None of the above seem to trigger the Retry. The failure relation seem to be triggered by query error and is working fine. My question is why the Retry is not getting triggered and what condition triggers it? Thanks
... View more
Labels:
- Labels:
-
Apache NiFi
08-07-2020
10:14 AM
Thank you very much! After installing the proper java version the Groovy script started to work.
... View more
08-06-2020
11:49 AM
OK, will try to install the required java version. My bad, I did not think that would cause the problem. Do I have to uninstall nifi and reinstall everything or just uninstalling\reinstalling java would suffice.? Thanks for your help
... View more
08-06-2020
11:11 AM
Im using single instance. I just ran the "java -version" command, and here is what I have: java version "14.0.1" 2020-04-14 Java(TM) SE Runtime Environment (build 14.0.1+7) Java HotSpot(TM) 64-Bit Server VM (build 14.0.1+7, mixed mode, sharing)
... View more
08-06-2020
08:44 AM
Thanks for attending to my ticket. Im using what I think the latest nifi version 1.11.4. Running on windows 10 for testing. I was using script similar to what is provided in (https://community.cloudera.com/t5/Community-Articles/ExecuteScript-Cookbook-part-1/ta-p/248922 ) which seems to be outdated because the scripting languages there doesnt match what I see in the latest version of Nifi. None the less when I try your script it still fails with the same error (other scripts engine like python works fine): ExecuteScript[id=c461682d-0173-1000-f3bb-1a7ace8e772d] ExecuteScript[id=c461682d-0173-1000-f3bb-1a7ace8e772d] failed to process session due to Could not initialize class org.codehaus.groovy.classgen.Verifier; Processor Administratively Yielded for 1 sec: java.lang.NoClassDefFoundError: Could not initialize class org.codehaus.groovy.classgen.Verifier
... View more
08-06-2020
06:59 AM
Anybody can help with this please? I cant progress without resolving this error which seems to be related to Nifi\groovy configuration that prevents me from running any kind of groovy script from nifi. Thanks
... View more
- « Previous
- Next »