hadoop kerberos官方配置详解(5)

下面的属性应该在集群中所有节点的core-site.xml文件中。

ParameterValueNotes
hadoop.security.authentication   kerberos   simple : No authentication. (default) kerberos : Enable authentication by Kerberos.  
hadoop.security.authorization   true   Enable RPC service-level authorization.  
hadoop.rpc.protection   authentication   authentication : authentication only (default); integrity : integrity check in addition to authentication; privacy : data encryption in addition to integrity  
hadoop.security.auth_to_local   RULE:exp1 RULE:exp2 … DEFAULT   The value is string containing new line characters. See Kerberos documentation for the format of exp.  
hadoop.proxyuser.superuser.hosts       comma separated hosts from which superuser access are allowed to impersonation. * means wildcard.  
hadoop.proxyuser.superuser.groups       comma separated groups to which users impersonated by superuser belong. * means wildcard.  
NameNode ParameterValueNotes
dfs.block.access.token.enable   true   Enable HDFS block access tokens for secure operations.  
dfs.namenode.kerberos.principal   nn/_HOST@REALM.TLD   Kerberos principal name for the NameNode.  
dfs.namenode.keytab.file   /etc/security/keytab/nn.service.keytab   Kerberos keytab file for the NameNode.  
dfs.namenode.kerberos.internal.spnego.principal   HTTP/_HOST@REALM.TLD   The server principal used by the NameNode for web UI SPNEGO authentication. The SPNEGO server principal begins with the prefix HTTP/ by convention. If the value is ‘*’, the web server will attempt to login with every principal specified in the keytab file dfs.web.authentication.kerberos.keytab. For most deployments this can be set to ${dfs.web.authentication.kerberos.principal} i.e use the value of dfs.web.authentication.kerberos.principal.  
dfs.web.authentication.kerberos.keytab   /etc/security/keytab/spnego.service.keytab   SPNEGO keytab file for the NameNode. In HA clusters this setting is shared with the Journal Nodes.  

下面的设置允许配置SSL访问NameNode的web UI(可选)。

ParameterValueNotes
dfs.http.policy   HTTP_ONLY or HTTPS_ONLY or HTTP_AND_HTTPS   HTTPS_ONLY turns off http access. This option takes precedence over the deprecated configuration dfs.https.enable and hadoop.ssl.enabled. If using SASL to authenticate data transfer protocol instead of running DataNode as root and using privileged ports, then this property must be set to HTTPS_ONLY to guarantee authentication of HTTP servers. (See dfs.data.transfer.protection.)  
dfs.namenode.https-address   nn_host_fqdn:50470      
dfs.https.port   50470      
dfs.https.enable   true   This value is deprecated. Use dfs.http.policy  
Secondary NameNode ParameterValueNotes
dfs.namenode.secondary.http-address   snn_host_fqdn:50090      
dfs.secondary.namenode.keytab.file   /etc/security/keytab/sn.service.keytab   Kerberos keytab file for the Secondary NameNode.  
dfs.secondary.namenode.kerberos.principal   sn/_HOST@REALM.TLD   Kerberos principal name for the Secondary NameNode.  
dfs.secondary.namenode.kerberos.internal.spnego.principal   HTTP/_HOST@REALM.TLD   The server principal used by the Secondary NameNode for web UI SPNEGO authentication. The SPNEGO server principal begins with the prefix HTTP/ by convention. If the value is ‘*’, the web server will attempt to login with every principal specified in the keytab file dfs.web.authentication.kerberos.keytab. For most deployments this can be set to ${dfs.web.authentication.kerberos.principal} i.e use the value of dfs.web.authentication.kerberos.principal.  
dfs.namenode.secondary.https-port   50470      
JournalNode ParameterValueNotes
dfs.journalnode.kerberos.principal   jn/_HOST@REALM.TLD   Kerberos principal name for the JournalNode.  
dfs.journalnode.keytab.file   /etc/security/keytab/jn.service.keytab   Kerberos keytab file for the JournalNode.  
dfs.journalnode.kerberos.internal.spnego.principal   HTTP/_HOST@REALM.TLD   The server principal used by the JournalNode for web UI SPNEGO authentication when Kerberos security is enabled. The SPNEGO server principal begins with the prefix HTTP/ by convention. If the value is ‘*’, the web server will attempt to login with every principal specified in the keytab file dfs.web.authentication.kerberos.keytab. For most deployments this can be set to ${dfs.web.authentication.kerberos.principal} i.e use the value of dfs.web.authentication.kerberos.principal.  
dfs.web.authentication.kerberos.keytab   /etc/security/keytab/spnego.service.keytab   SPNEGO keytab file for the JournalNode. In HA clusters this setting is shared with the Name Nodes.  
DataNode ParameterValueNotes
dfs.datanode.data.dir.perm   700      
dfs.datanode.address   0.0.0.0:1004   Secure DataNode must use privileged port in order to assure that the server was started securely. This means that the server must be started via jsvc. Alternatively, this must be set to a non-privileged port if using SASL to authenticate data transfer protocol. (See dfs.data.transfer.protection.)  
dfs.datanode.http.address   0.0.0.0:1006   Secure DataNode must use privileged port in order to assure that the server was started securely. This means that the server must be started via jsvc.  
dfs.datanode.https.address   0.0.0.0:50470      
dfs.datanode.kerberos.principal   dn/_HOST@REALM.TLD   Kerberos principal name for the DataNode.  
dfs.datanode.keytab.file   /etc/security/keytab/dn.service.keytab   Kerberos keytab file for the DataNode.  
dfs.encrypt.data.transfer   false   set to true when using data encryption  
dfs.encrypt.data.transfer.algorithm       optionally set to 3des or rc4 when using data encryption to control encryption algorithm  
dfs.encrypt.data.transfer.cipher.suites       optionally set to AES/CTR/NoPadding to activate AES encryption when using data encryption  
dfs.encrypt.data.transfer.cipher.key.bitlength       optionally set to 128, 192 or 256 to control key bit length when using AES with data encryption  
dfs.data.transfer.protection       authentication : authentication only; integrity : integrity check in addition to authentication; privacy : data encryption in addition to integrity This property is unspecified by default. Setting this property enables SASL for authentication of data transfer protocol. If this is enabled, then dfs.datanode.address must use a non-privileged port, dfs.http.policy must be set to HTTPS_ONLY and the HADOOP_SECURE_DN_USER environment variable must be undefined when starting the DataNode process.  
WebHDFS ParameterValueNotes
dfs.web.authentication.kerberos.principal h   ttp/_HOST@REALM.TLD   Kerberos principal name for the WebHDFS. In HA clusters this setting is commonly used by the JournalNodes for securing access to the JournalNode HTTP server with SPNEGO.  
dfs.web.authentication.kerberos.keytab   /etc/security/keytab/http.service.keytab   Kerberos keytab file for WebHDFS. In HA clusters this setting is commonly used the JournalNodes for securing access to the JournalNode HTTP server with SPNEGO.  
ResourceManager ParameterValueNotes
yarn.resourcemanager.principal   rm/_HOST@REALM.TLD   Kerberos principal name for the ResourceManager.  
yarn.resourcemanager.keytab   /etc/security/keytab/rm.service.keytab   Kerberos keytab file for the ResourceManager.  
NodeManager ParameterValueNotes
yarn.nodemanager.principal   nm/_HOST@REALM.TLD   Kerberos principal name for the NodeManager.  
yarn.nodemanager.keytab   /etc/security/keytab/nm.service.keytab   Kerberos keytab file for the NodeManager.  
yarn.nodemanager.container-executor.class   org.apache.hadoop.yarn.server.nodemanager.LinuxContainerExecutor   Use LinuxContainerExecutor.  
yarn.nodemanager.linux-container-executor.group   hadoop   Unix group of the NodeManager.  
yarn.nodemanager.linux-container-executor.path   /path/to/bin/container-executor   The path to the executable of Linux container executor.  
WebAppProxy配置

内容版权声明:除非注明,否则皆为本站原创文章。

转载注明出处:https://www.heiqu.com/d9d246ed39d4b7719eccfada3af60d5c.html