About nismaily

nismaily · ‎08-19-2019

This article describes the configuration of the authorizers.xml for using the Composite User Group Provider for both LDAP and File based authentication in Cloudera Manager for CDF 1.0 This article assumes TLS has already been configured for NiFi using either the NiFi CA or your own certs. Here is the Active Directory Structure that I will use for my sync: Here are the groups in the Groups OU: Here are the users in the Users OU: Here are the service users in the ServiceUsers OU: First, I will import my Active Directory root certificate into the NiFi and Java Truststores: keytool -import -file adcert.pem -alias ad -keystore /var/lib/nifi/cert/truststore.jks keytool -import -file adcert.pem -alias ad -keystore /etc/pki/java/cacerts Now login to Cloudera Manager and proceed to the NiFi Configuration. Update the configuration to use the "composite-user-group-provider" as follows: xml.authorizers.accessPolicyProvider.file-access-policy-provider.property.User Group Provider=composite-user-group-provider Next, use the "NiFi Node Advanced Configuration Snippet (Safety Valve) for staging/authorizers.xml" and add the following configurations using the XML view: <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.class</name> <value>org.apache.nifi.ldap.tenants.LdapUserGroupProvider</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Manager DN</name> <value>CN=ldapbind-svc,OU=ServiceUsers,OU=CLDR,DC=nismaily,DC=com</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Manager Password</name> <value>hadoop</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Referral Strategy</name> <value>FOLLOW</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Connect Timeout</name> <value>10 secs</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Read Timeout</name> <value>10 secs</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Url</name> <value>ldaps://win-ltfjo4jgo4r.nismaily.com:636</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Sync Interval</name> <value>15 mins</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.User Search Base</name> <value>OU=Users,OU=CLDR,DC=nismaily,DC=com</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.User Object Class</name> <value>user</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.User Search Scope</name> <value>SUBTREE</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.User Identity Attribute</name> <value>sAMAccountName</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.User Group Name Attribute</name> <value>memberof</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Group Search Base</name> <value>OU=Groups,OU=CLDR,DC=nismaily,DC=com</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Group Object Class</name> <value>group</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Group Search Scope</name> <value>SUBTREE</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Group Name Attribute</name> <value>cn</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Group Member Attribute</name> <value>member</value> </property> <property> <name>xml.authorizers.userGroupProvider.composite-user-group-provider.class</name> <value>org.apache.nifi.authorization.CompositeConfigurableUserGroupProvider</value> </property> <property> <name>xml.authorizers.userGroupProvider.composite-user-group-provider.property.Configurable User Group Provider</name> <value>file-user-group-provider</value> </property> <property> <name>xml.authorizers.userGroupProvider.composite-user-group-provider.property.User Group Provider 1</name> <value>ldap-user-group-provider</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.Authentication Strategy</name> <value>LDAPS</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Keystore</name> <value>/var/lib/nifi/cert/keystore.jks</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Keystore Password</name> <value>hadoop</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Keystore Type</name> <value>jks</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Truststore</name> <value>/var/lib/nifi/cert/truststore.jks</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Truststore Password</name> <value>hadoop</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Truststore Type</name> <value>jks</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Client Auth</name> <value>WANT</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Protocol</name> <value>TLSv1.2</value> </property> <property> <name>xml.authorizers.userGroupProvider.ldap-user-group-provider.property.TLS - Shutdown Gracefully</name> <value>false</value> </property> Restart NiFi and login to the NiFi UI. Proceed to the Users Tab: You will see the users synced from Active Directory:

nismaily · ‎06-24-2017

Try this: sqoop import \ --username username \ --P \ --connect jdbc:sap://hostname:portnumber/ \ --driver com.sap.db.jdbc.Driver \ --query "select * from \"schema\".\"/path/to/hana/calculation\" where \$CONDITIONS" \ --hcatalog-database hivedatabase \ --hcatalog-table hivetable \ --create-hcatalog-table \ --hcatalog-storage-stanza "stored as orc"

nismaily · ‎05-26-2017

This Is Amazing, thanks for posting this !

nismaily · ‎03-25-2017

Did you copy the ojdbc jar to the nifi lib directory and restart nifi?

nismaily · ‎12-21-2016

What is the correct process in moving the Journal Node Directories to a different disk? Lets say I have 3 servers, each running a Journal Node Service: server1 server2 server3 The Journal Nodes are currently writing to /var/lib/hadoop/hdfs/journal I want to change this to /data1/hadoop/hdfs/journal for each server I've tried: 1) Stopping Namenodes (HA) 2) Copying data from /var/lib/hadoop/hdfs/journal to /data1/hadoop/hdfs/journal 3) Changing the dir property for the Journal Nodes in Ambari 4) Starting the Namenodes This did not seem to work

nismaily · ‎12-21-2016

Edit the following file: /etc/ambari-server/conf/ambari.properties Increase the following parameters: views.request.connect.timeout.millis views.request.read.timeout.millis Restart Ambari Server

nismaily · ‎11-08-2016

I increased the capacity and it worked, thanks!

nismaily · ‎11-03-2016

I'm having trouble getting Hive Interactive (LLAP) to work I'm working on a kerberized HDP 2.5 cluster. It seems like only 1 daemon starts, here's the error: 2016-11-03 15:50:50,084 - Marker index for start of JSON data for 'llapsrtatus' comamnd : 0 2016-11-03 15:50:50,085 - LLAP app 'llap0' in 'RUNNING_PARTIAL' state. Live Instances : '1'. Desired Instances : '4' after 221.781697989 secs. 2016-11-03 15:50:50,085 - LLAP app 'llap0' did not come up after a wait of 221.782001972 seconds. 2016-11-03 15:50:50,087 - LLAP app 'llap0' deployment unsuccessful. What is the cause for this?

nismaily · ‎06-01-2016

Thanks Ravi, I had to: 1) Copy spark shuffle jars to nodemanager classpaths on all nodes 2) add spark_shuffle to yarn.nodemanager.aux-services, set yarn.nodemanager.aux-services.spark_shuffle.class to org.apache.spark.network.yarn.YarnShuffleService in yarn-site.xml (via Ambari) 3) Restart all nodemanagers 4) Add the following to spark-defaults.conf spark.dynamicAllocation.enabled true spark.shuffle.service.enabled true 5) Set these parameters per job basis spark.dynamicAllocation.initialExecutors=# spark.dynamicAllocation.minExecutors=#

nismaily · ‎05-25-2016

Thanks Ravi, this is very close to what I need. Question, spark.dynamicAllocation.minExecutors seems to be a global property in spark-defautls Is there a way to set this property on a job by job basis? Spark job1 -> min executors 8 Spark job2 -> min executors 5

Online	Offline
Last Visited	‎10-13-2022 03:28 PM

Member Since	‎04-11-2016 05:39 PM
Last Visited	‎10-13-2022 03:28 PM
Posts	32
Kudos received	21

Cloudera Community

Cloudera Community

Re: Ingesting calculation views from Hana into Hiv...

Re: Nifi Oracle JDBC Connection Issue

Re: tez view timeout

Re: Spark - YARN Capacity Scheduler

Re: Storm Bolt throws an error when trying to read...

NiFi Composite Authorization - LDAP and File - Usi...

Re: Ingesting calculation views from Hana into Hiv...

Re: Using a local instance of Cloudbreak with Vagr...

Re: Nifi Oracle JDBC Connection Issue

Moving Journal Node Directories

Re: tez view timeout

Re: Hive LLAP fails to start with RUNNING_PARTIAL ...

Hive LLAP fails to start with RUNNING_PARTIAL stat...

Re: Spark - YARN Capacity Scheduler

Re: Spark - YARN Capacity Scheduler