Member since
09-29-2015
362
Posts
242
Kudos Received
63
Solutions
My Accepted Solutions
| Title | Views | Posted |
|---|---|---|
| 1822 | 03-14-2019 01:00 PM | |
| 2110 | 01-23-2019 04:19 PM | |
| 8612 | 01-15-2019 01:59 PM | |
| 6318 | 01-15-2019 01:57 PM | |
| 15287 | 12-06-2018 02:01 PM |
12-21-2016
10:21 AM
2 Kudos
@Jacqualin jasmin The answers to your questions are related to how you set up your KDC. Technically the realm name can be anything, but should at least be in all uppercase characters. Typically realm names match or are similar to domain names. For you, you might use CORP.INFINITY.COM or maybe HADOOP.INFINITY.COM if you wanted to be explicit on the usage of the principals in the realm. It could also be totally random, like MY.REALM. In any case, when filling in the forms in the Enable Kerberos Wizard you would add the following to the domains field in order to create a mapping from the domain names in your cluster to the realm name: corp.infinity.com, .corp.infinity.com The administrator credentials are relative to the accounts in the KDC. Just like any other account in any other system, the user that installs and manages the KDC will create this and have this information. Typically the administrator accounts will have a "/admin" attached to it for various reasons: to easily visually identify this as an administrator account and to easily set the ACLs in the KDC (depending on the KDC you are using). I typically use "admin/admin" as the principal name (with my realm name attached - for example admin/admin@EXAMPLE.COM. But this is all relative and it can also be any account as long as the KDC is set up to use that as an administrator account. For example jjasmin@EXAMPLE.COM. When I use the acronym "KDC", this included generic KDCs like the MIT KDC as well as the an Active Directory. Here is a script the can help install an MIT KDC - this one is for Centos6, but I have them for other Linux flavors as well - install-kdcsh.txt (rename this to install-kdc.sh). This installs an MIT KDC with the realm EXAMPLE.COM and an administrator account with: Principal: admin/admin@EXAMPLE.COM Password: hadoop If you walk through Ambari's Enable Kerberos Wizard, it will prompt you for information it needs. Once complete it will set up the krb5.conf files, create the necessary principals, and distribute the required keytab files. You just need to set up the KDC and provide the details about that - host where the KDC is installed, type of KDC, realm, and administrator credentials.
... View more
11-30-2016
04:26 PM
kdc = hadoop1 should probably be kdc = hadoop1.tolls.dot.state.fl.us
... View more
11-30-2016
04:23 PM
@Sami Ahmad It seems like your KDC installation is all messed up. Can you remove the client and server packages as well as the /var/kerberos directory and its contents? Then try to reinstall it. Here is a script that I use for Centos6. If you have a different OS, let me know and I might have a script for that. In any case the script creates a KDC with the realm of EXAMPLE.COM. You can edit the script to change this. It also creates an administrator principal - admin/admin@EXAMPLE.COM (password: admin). install-kdcsh.txt
... View more
11-30-2016
02:31 PM
@Sami Ahmad Looking at the error: 29 Nov 2016 15:49:43,526 WARN [ambari-client-thread-1242] MITKerberosOperationHandler:459 - Failed to execute kadmin:
Command: [/usr/bin/kadmin, -s, hadoop1.tolls.dot.state.fl.us, -p, K/M@TOLLS.DOT.STATE.FL.US, -r, TOLLS.DOT.STATE.FL.US, -q, get_principal K/M@TOLLS.DOT.STATE.FL.US]
ExitCode: 1
STDOUT: Authenticating as principal K/M@TOLLS.DOT.STATE.FL.US with password.
STDERR: kadmin: Clients credentials have been revoked while initializing kadmin interface It appears that the admin account you are using has been locked out. See http://web.mit.edu/Kerberos/krb5-1.13/doc/admin/lockout.html for more information on this.
... View more
11-29-2016
02:23 PM
You are correct. It appears that by default Ambari's CA cert is value for 365 days. See https://github.com/apache/ambari/blob/2ad42074f1633c5c6f56cf979bdaa49440457566/ambari-server/src/main/java/org/apache/ambari/server/security/CertificateManager.java#L54 private static final String SIGN_SRVR_CRT = "openssl ca -create_serial " +
"-out {1}" + File.separator + "{3} -days 365 -keyfile {1}" + File.separator + "{2} -key {0} -selfsign " +
"-extensions jdk7_ca -config {1}" + File.separator + "ca.config -batch " +
"-infiles {1}" + File.separator + "{5}";
Notice: -days 365
... View more
11-29-2016
02:22 PM
You are correct. It appears that by default Ambari's CA cert is value for 365 days. See https://github.com/apache/ambari/blob/2ad42074f1633c5c6f56cf979bdaa49440457566/ambari-server/src/main/java/org/apache/ambari/server/security/CertificateManager.java#L54 private static final String SIGN_SRVR_CRT = "openssl ca -create_serial " +
"-out {1}" + File.separator + "{3} -days 365 -keyfile {1}" + File.separator + "{2} -key {0} -selfsign " +
"-extensions jdk7_ca -config {1}" + File.separator + "ca.config -batch " +
"-infiles {1}" + File.separator + "{5}";
Notice: -days 365
... View more
11-28-2016
10:09 PM
@apappu, Steps 1 through 3 are only needed if the CA cert generated by Ambari is expired. If it is not expired, then only steps 4, 5, and 7 should be needed. Did you verify that the Ambari-generated CA cert was expired.
... View more
10-17-2016
02:23 PM
Your question seems to be unclear. Where are you looking to reset the admin password... from within the credentials stored in Ambari (if you enabled that) or within the KDC (or Active Directory, etc...)? You cannot enable Kerberos without the credentials for some privileged user in the KDC unless you select the "manual" option, in which you will be responsible for the principal and keytab file creation and distribution.
... View more
10-14-2016
10:32 AM
3 Kudos
@Sarah Maadawy I agree with @Kuldeep Kulkarni regarding the principal name used for the HDFS Kerberos identity. However on top of that, you should su to the hdfs user to do this. The existence of the HDFS keytab file is not meant to be used by any other user. Why is the owner of /etc/security/keytabs/hdfs.headless.keytab root? Does Ambari manage the Kerberos identities of your cluster or were the keytab files created and distributed manually? In any case the ACL on that file should be like -r--r----- 1 hdfs hadoop 303 Oct 12 15:16 /etc/security/keytabs/hdfs.headless.keytab Or ideally -r-------- 1 hdfs hadoop 303 Oct 12 15:16 /etc/security/keytabs/hdfs.headless.keytab However I think some Hadoop services may need access to this keytab file for now.
... View more
09-19-2016
03:50 PM
If the cluster is Kerberized, then some, if not all views, will require that Ambari's Kerberos identity is configured. This is so the views can authenticate to the relevant services.
... View more