Member since
05-17-2016
190
Posts
46
Kudos Received
11
Solutions
My Accepted Solutions
Title | Views | Posted |
---|---|---|
1257 | 09-07-2017 06:24 PM | |
1639 | 02-24-2017 06:33 AM | |
2328 | 02-10-2017 09:18 PM | |
6820 | 01-11-2017 08:55 PM | |
4247 | 12-15-2016 06:16 PM |
12-07-2022
09:46 PM
While converting from json to avro format,how to get logicaltype in avro format. And to get logicaltype in avro format,what we need to add in json data .
... View more
04-21-2021
03:45 AM
Sorry it's max 8060 characters
... View more
02-23-2021
02:01 AM
I'm new to NiFi, and I'm not sure your data flow has same condition as mine, but I have a same issue of being occurred the same exception that you mentioned. I'm using Oracle 11g XE, there was no invalid query nor invalid data. In addition, I had another problem with the Oracle session of PutSQL been locked when I let a lot of flowfile flow to PutSQL processor, e.g., 5,000 flowfile in 0.5 sec. I have spent all day long to fix this problem today modifying almost every single properties of all processors connected to the flow, and even of DBCP controller service... and finally found the cause. In processor PutSQL, there is a property named 'Support Fragmented Transactions'. I don't know pretty much about this and need to know how it works, but when I have set it false, the problem was solved. And it took some time more than before. I'm not an expert of NiFi, but I hope this might be helpful for you.
... View more
08-19-2020
10:01 AM
https://www.datainmotion.dev/2020/08/deleting-schemas-from-cloudera-schema.html
... View more
02-26-2020
12:00 AM
in the schema definition for name and address set "default" : "null" instead of "default": null
... View more
01-12-2020
05:46 PM
Thanks Steven, I removed the hostname and it started working after I set hostname box empty.
... View more
06-14-2018
11:28 PM
Output Data of the form
... View more
09-04-2018
02:23 AM
The issue is resolved and i was able to fix it by enabling network access from AL for sandbox build.
... View more
10-02-2018
01:04 PM
@Arun A K The "ldap-user-group-provider" is not passed any input, so using things like (cn={0}) will not work. This is perfectly valid in the login-identity-providers.xml since it is being passed the login name the user enters on login screen. <userGroupProvider>
<identifier>ldap-user-group-provider</identifier> <class>org.apache.nifi.ldap.tenants.LdapUserGroupProvider</class> <property name="Authentication Strategy">SIMPLE</property> <property name="Manager DN">uid=admin,cn=blah,cn=blah,dc=blah,dc=com</property> <property name="Manager Password">blah</property> <property name="TLS - Keystore"></property> <property name="TLS - Keystore Password"></property> <property name="TLS - Keystore Type"></property> <property name="TLS - Truststore"></property> <property name="TLS - Truststore Password"></property> <property name="TLS - Truststore Type"></property> <property name="TLS - Client Auth"></property> <property name="TLS - Protocol"></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://blah.ldap.com:389</property> <property name="Page Size"></property> <property name="Sync Interval">30 mins</property> <property name="User Search Base">cn=users,cn=accounts,dc=blah,dc=blah,dc=com</property> <property name="User Object Class">person</property> <property name="User Search Scope">SUBTREE</property> <property name="User Search Filter"></property> <property name="User Identity Attribute">uid</property> <property name="User Group Name Attribute">memberOf</property> <property name="User Group Name Attribute - Referenced Group Attribute"></property> <property name="Group Search Base">cn=groups,cn=accounts,dc=blah,dc=blah,dc=com</property> <property name="Group Object Class">posixgroup</property> <property name="Group Search Scope">SUBTREE</property> <property name="Group Search Filter"></property> <property name="Group Name Attribute">cn</property> <property name="Group Member Attribute">member</property> <property name="Group Member Attribute - Referenced User Attribute"></property>
</userGroupProvider> The above is what you should have at a minimum. You may need to also specify the two "Referenced User/Group Attribute" values, but can't tell from your sample LDAP output is that is really going to be necessary. - Thanks, Matt
... View more
02-16-2018
05:48 PM
3 Kudos
In this article, we will have a walk through of integrating LDAP with NiFi Registry. The precondition for LDAP to work with NiFi-Registry is that SSL need to be enabled. This article also covers the "How To" enable SSL for NiFI Registry. For the sake of simplicity, I am using self signed certificates (JKS, using keytool). Steps for creating self signed certificates are as below :- Generate KeyStore keytool -genkey -keyalg RSA -validity 3650 -alias <alias_name> -keypass <pwd> -storepass <pwd> -dname "cn=hostname, ou=home, o=ak, c=us" -keystore nifi_reg_keystore.jks Export a certificate with the public key keytool -export -alias <alias_name> -file nifi_reg.cer -storepass <pwd> -keystore nifi_reg_keystore.jks Generate TrustStore keytool -import -noprompt -alias nr-c0 -file nifi_reg.cer -storepass changeitchangeit -keystore nifi_reg_truststore.jks
Below, is a representation of the NiFi Registry UI with default http and anonymous user login. Now we will login to Ambari and use the above generated certificate details to complete setting up SSL. On the configuration tab, search for the SSL settings. The section to be edited is as below:- Populate the form with the details of the truststore and keystore that we generated above. At this stage, SSL setup for NiFi Registry is complete, however we have't assigned any users to login to the UI. Either we generate a certificate for an Initial Admin, or create an initial admin from the LDAP user base. We will use an LDAP user as the Initial Admin for the NiFi Registry. The configuration information for the same is as below, There are 4 sections that need to be edited, Configure Initial Admin Configure Security Identity Provider (nifi.registry.security.identity.provider) Configure login-identity-providers.xml
Remove the 2 lines that say
To enable the ldap-identity-provider remove 2 lines. This is 1 of 2. To enable the ldap-identity-provider remove 2 lines. This is 2 of 2. Fill details specific to your LDAP server. I am using a SIMPLE auth strategy with a non ssl LDAP server. Below are relevant sections from my configuration window
Configure authorizers.xml
Remove the 2 lines that say
To enable the ldap-user-group-provider remove 2 lines. This is 1 of 2. To enable the ldap-user-group-provider remove 2 lines. This is 2 of 2. Configure ldap-user-group-provider Configure accessPolicyProvider The below screenshot shows the relevant section for configuring the ldap-user-group-provider Screenshot below shows the configuration changes needed to the access policy provider. Set User Group Provider to ldap-user-group-provider. At this stage, we are in a position to save all the configuration changes and restart the NiFI Registry services. Follow the Ambari prompts and you should see as below Now we should be good to access the NiFi Registry UI and login as the Initial Admin that is configured. guest1 in my example. Access NiFi Registry UI from Quick Links Login Using the Initial Admin Credentials Verify login is successful Verify users are available/sync-ed You should be able to proceed using the NiFi registry from here on.
... View more
Labels: