You only need to restart the CM server after uploading the new license file, please refer:   ==> https://docs.cloudera.com/documentation/enterprise/6/6.3/topics/cm_ag_licenses.html#cmug_topic_13_7__section_jt4_ynp_wr   ... View more

This needs to be done from LDAP/AD side. Create a group in LDAP for the users you want to give access to the CM and sync only that group in CM using the group filter. ... View more

Hey follow the below doc: https://docs.cloudera.com/cdp-private-cloud-base/7.1.6/security-kerberos-authentication/topics/cm-security-external-authentication-ldap.html   Administration   >   Settings >  Authentication Backend Order > select the appropriate one eg: External Only (with emergency Administrator access) ... View more

This is not a SSL related issue. For, RHEL 6.7, need RHEL 6 repo: https://archive.cloudera.com/p/cdh5/redhat/6/x86_64/cdh/5.16.2/ // you are using the RHEL7 repo. Can you check a few things from the YUM/OS side: 1. Are you behind firewall/proxy? 2.  Are you able to access any other public repos? 3. Try,      # yum clean all      # yum repolist -v   Important notice: The support for CDH 5.16.x ended on December 2020. refer: https://www.cloudera.com/legal/policies/support-lifecycle-policy.html ... View more

Yeah, this should work. Also, if you want to verify the complete configuration, I would recommend contacting Cloudera technical support: ==> https://my.cloudera.com/faq/support.html ... View more

Are you able to  Decommission the DN or NM? refer: https://docs.cloudera.com/HDPDocuments/Ambari-2.7.3.0/managing-and-monitoring-ambari/content/amb_decommission_a_nodemanager.html https://docs.cloudera.com/HDPDocuments/Ambari-2.7.3.0/managing-and-monitoring-ambari/content/amb_decommission_a_datanode.html   To delete the host: https://docs.cloudera.com/HDPDocuments/Ambari-2.6.1.5/bk_ambari-operations/content/deleting_a_host_from_a_cluster.html   Note: Turn off host Maintenance Mode, before deleting the host ... View more

Have you checked: https://docs.cloudera.com/cdp-private-cloud/latest/upgrade-hdp/topics/amb-hdp-cdp-upg.html ... View more

Configuration should be like this:   Realm Name: ABC.EXAMPLE.COM domain_realm: .example.com = ABC.EXAMPLE.COM example.com =  ABC.EXAMPLE.COM Usually, the realm name should be configured when you set up AD. I would recommend checking with your AD team to get the mapping details. Also, time should be synced. ... View more

By default, the name of the realm is taken to be the DNS domain name of the server in all capital letters. foo.example.org → EXAMPLE.ORG foo.example.com → EXAMPLE.COM foo.hq.example.com → HQ.EXAMPLE.COM In some configurations, this will be sufficient, but in others, the realm name which is derived will be the name of a non-existent realm. In these cases, the mapping from the server's DNS domain name to the name of its realm must be specified in the   domain_realm   section of the client system's   krb5.conf. For example: [domain_realm] .example.com = EXAMPLE.COM example.com = EXAMPLE.COM The configuration specifies two mappings. The first mapping specifies that any system in the example.com DNS domain belongs to the   EXAMPLE.COM   realm. The second specifies that a system with the exact name example.com is also in the realm Also, time should be correct/synced in all servers. ... View more