Created 05-03-2017 06:30 AM
Are their any rules or limitations while creating password in hadoop cluster. If yes, is their any documentation available for the same.
Created 05-03-2017 07:14 AM
Could you please clarify on what passwords you are referring here? We dont have any password authentication for hadoop(HDFS/YARN/MR). What ever user authenticated on client host(where executing hdfs command) will be the user accessing hadoop services. (Using kerberos is regular practise to configure authentication on hadoop)
Created 05-03-2017 07:14 AM
Could you please clarify on what passwords you are referring here? We dont have any password authentication for hadoop(HDFS/YARN/MR). What ever user authenticated on client host(where executing hdfs command) will be the user accessing hadoop services. (Using kerberos is regular practise to configure authentication on hadoop)
Created 05-03-2017 07:23 AM
I want to create on a kerberos hadoop cluster. Do we have rules for that?
like not adding a paranthesis or something?
Created 05-03-2017 08:06 AM
hadoop doesnt enforce any rules, if using AD for kerberos, usually password policies are set in AD. No such requirement from hadoop end. We just need a principal created in AD/KDC. Only recommendation is to set "password never expire" for the service account created in AD.
Created 05-03-2017 08:20 AM
thanks
Created 07-12-2018 11:06 AM
The only limitation i ran into so far was the password of my LDAP Manager / Bind user within Apache Ranger UserSync.
I got the following error message after I applied the correct AD Settings to UserSync:
resource_management.core.exceptions.Fail: LDAP/AD bind password contains one of the unsupported special characters like " ' \ `
Created 11-21-2019 06:41 AM
I'm having a similar issue with the YARN clients in my cluster. When the password is set in Ambari and it has a special character of ">" the YARN Client interprets it as ">".
Example:
Set passwd - ba(PxO463$bd;>
Passwd in the yarn core-site.xml
lx963:/usr/hdp/2.6.5.0-292/hadoop-yarn/etc/hadoop #grep PxO463$bd core-site.xml
<value>ba(PxO463$bd;></value>
<value>ba(PxO463$bd;></value>
Is there a workaround or fix for this?