Configuración de la autenticación de Kerberos con KDC local y KDC de Active Directory

El cluster de Big Data Service aprovisiona el KDC local del MIT por defecto. El cluster también se puede aprovisionar para utilizar el KDC de Active Directory para usuarios que pertenecen al dominio de Active Directory. También debe configurar la confianza cruzada entre los dos dominios.

Actualización de Ambari para utilizar el KDC de Active Directory

  1. Acceda a Apache Ambari.
  2. En la barra de herramientas lateral, en Cluster Admin (Administrador de cluster), seleccione Kerberos.
  3. Seleccione el separador Configs y, a continuación, amplíe la sección Advanced krb5-conf.
  4. Modifique el campo krb5-conf template de forma similar al siguiente contenido:
    {#
    # Licensed to the Apache Software Foundation (ASF) under one
    # or more contributor license agreements.  See the NOTICE file
    # distributed with this work for additional information
    # regarding copyright ownership.  The ASF licenses this file
    # to you under the Apache License, Version 2.0 (the
    # "License"); you may not use this file except in compliance
    # with the License.  You may obtain a copy of the License at
    #
    #   http://www.apache.org/licenses/LICENSE-2.0
    #
    # Unless required by applicable law or agreed to in writing, software
    # distributed under the License is distributed on an "AS IS" BASIS,
    # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
    # See the License for the specific language governing permissions and
    # limitations under the License.
    #}
    [libdefaults]
      renew_lifetime = 7d
      forwardable = true
      default_realm = {{realm}}
      ticket_lifetime = 24h
      dns_lookup_realm = false
      dns_lookup_kdc = false
      #default_ccache_name = /tmp/krb5cc_%{uid}
      #default_tgs_enctypes = {{encryption_types}}
      #default_tkt_enctypes = {{encryption_types}}
    {% if domains %}
    [domain_realm]
    {%- for domain in domains.split(',') %}
      {{domain|trim()}} = {{realm}}
    {%- endfor %}
    {% endif %}
      example.oraclevcn.com = <ad-realm>
     
    [logging]
      default = FILE:/var/log/krb5kdc.log
      admin_server = FILE:/var/log/kadmind.log
      kdc = FILE:/var/log/krb5kdc.log
     
    [realms]
      {{realm}} = {
    {%- if master_kdc %}
        master_kdc = {{master_kdc|trim()}}
    {%- endif -%}
    {%- if kdc_hosts > 0 -%}
    {%- set kdc_host_list = kdc_hosts.split(',')  -%}
    {%- if kdc_host_list and kdc_host_list|length > 0 %}
        admin_server = {{admin_server_host|default(kdc_host_list[0]|trim(), True)}}
    {%- if kdc_host_list -%}
    {%- if master_kdc and (master_kdc not in kdc_host_list) %}
        kdc = {{master_kdc|trim()}}
    {%- endif -%}
    {% for kdc_host in kdc_host_list %}
        kdc = {{kdc_host|trim()}}
    {%- endfor -%}
    {% endif %}
    {%- endif %}
    {%- endif %}
      }
     
    {# Append additional realm declarations below #}
      <ad-realm> = {
        admin_server = server-example.oraclevcn.com:749
        kdc = kdc-example.oraclevcn.com:88
        default_domain = domain-example.oraclevcn.com
      }
     
    [capaths]
    <ad-realm> = {
    <your-local-realm> = .
    }
  5. Guarde la configuración y reinicie todos los servicios afectados.
  6. Vaya a HDFS > Configs > Advanced > Advanced core-site.
  7. Cambie el parámetro hadoop.security.auth_to_local para incluir lo siguiente:
    RULE:[1:$1@$0](.*@<ad-realm>)s/@.*//

    Ejemplo:

    RULE:[2:$1@$0](yarn@EXAMPLE.ORACLE.COM)s/.*/yarn/
    RULE:[2:$1@$0](yarn-ats-hbase@EXAMPLE.ORACLE.COM)s/.*/yarn-ats/
    RULE:[1:$1@$0](.*@EXAMPLE.REALM)s/@.*//
    DEFAULT