Member since
09-20-2017
49
Posts
3
Kudos Received
3
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 2833 | 02-14-2019 12:54 PM | |
| 3366 | 02-13-2019 08:32 AM | |
| 2083 | 01-28-2019 11:42 PM |
02-14-2019
12:54 PM
I managed to fix this by configuring CompositeGroupMapping instead of LdapGroupMapping.
... View more
02-13-2019
08:32 AM
core-site.xml had empty values not *. No issue.
... View more
02-12-2019
04:15 AM
Hello @bgooley Cross-realm trust is OK. I can `kinit` principals from both MIT KDC and AD realms. Hue-LDAP authenticaion is also OK, however (for now) LDAP users can only perform action not related to HDFS, HIVE and IMPALA. My target is to have some users (humans) to be authenticated against LDAP (for Hue and all CLI hive-impala-etc actions) and some other users (oozie pipelines) as well as all services to be authenticated against MIT KDC. Now, I am reading here https://www.cloudera.com/documentation/enterprise/5-15-x/topics/cm_sg_ldap_grp_mappings.html that: "The local user:group accounts must be mapped to LDAP for group mappings in Hadoop. You must create the users and groups for your Hadoop services in LDAP. To integrate the cluster with an LDAP service, the user:group relationships must be contained in the LDAP directory. The admin must create the user accounts and define groups for user:group relationships on each host." This is confusing, as it is supposed (https://www.cloudera.com/documentation/enterprise/5-14-x/topics/sg_auth_overview.html#concept_n5q_5h2_bt__local-mit-to-active-dir-architecture) that only user principals should be configured in AD. My question is whether in this architecture I need to define services user:group relationships etc in LDAP. (for User-group mapping I am trying both LdapGroupsMapping and SSSD - none have worked yet though) Thank you, Gerasimos
... View more
02-08-2019
08:26 AM
I'm glad that was it because I couldn't figure out many other possible causes of that sort of behavior :-).
... View more
01-28-2019
11:42 PM
1 Kudo
The problem was on StreamSets, where I had not disabled Kerberos. Now the Enable Kerberos option is active again.
... View more