From issues-return-66248-archive-asf-public=cust-asf.ponee.io@ambari.apache.org Fri Feb 2 19:00:06 2018 Return-Path: X-Original-To: archive-asf-public@eu.ponee.io Delivered-To: archive-asf-public@eu.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by mx-eu-01.ponee.io (Postfix) with ESMTP id D8CD0180608 for ; Fri, 2 Feb 2018 19:00:06 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id C8217160C49; Fri, 2 Feb 2018 18:00:06 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 1E815160C25 for ; Fri, 2 Feb 2018 19:00:05 +0100 (CET) Received: (qmail 14307 invoked by uid 500); 2 Feb 2018 18:00:05 -0000 Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list issues@ambari.apache.org Received: (qmail 14294 invoked by uid 99); 2 Feb 2018 18:00:05 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Feb 2018 18:00:05 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id DBACF1A0683 for ; Fri, 2 Feb 2018 18:00:04 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -101.511 X-Spam-Level: X-Spam-Status: No, score=-101.511 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id dLabt5lC8MOp for ; Fri, 2 Feb 2018 18:00:03 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 491925FAC8 for ; Fri, 2 Feb 2018 18:00:03 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 7A38EE02F1 for ; Fri, 2 Feb 2018 18:00:02 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 6D6CB240AA for ; Fri, 2 Feb 2018 18:00:00 +0000 (UTC) Date: Fri, 2 Feb 2018 18:00:00 +0000 (UTC) From: "Robert Levas (JIRA)" To: issues@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-22803) Update Hadoop RPC Encryption Properties During Kerberization and Upgrade MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-22803?page=3Dcom.atlass= ian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-22803: ---------------------------------- Description:=20 When *HDP 3.0.0* is installed, clients should have the ability to choose en= crypted communication over RPC when talking to core hadoop components. Toda= y, the properties that control this are: - {{core-site.xml : hadoop.rpc.protection =3D authentication}} - {{hdfs-site.xml : dfs.data.transfer.protection =3D authentication}} The new value of=C2=A0{{privacy}}=C2=A0enables clients to choose an encrypt= ed means of communication. By keeping=C2=A0{{authentication}}=C2=A0first, i= t will be taken as the default mechanism so that wire encryption is not aut= omatically enabled by accident. The following properties should be changed to add=C2=A0{{privacy}}: - {{core-site.xml : hadoop.rpc.protection =3D authentication,privacy}} - {{hdfs-site.xml : dfs.data.transfer.protection =3D authentication,privac= y}} The following are cases when this needs to be performed: - During Kerberization, the above two properties should be automatically r= econfigured. - During a stack upgrade to any version of HDP 2.6, they should be automat= ically merged Blueprint deployment is not a scenario being covered here. was: Clients should have the ability to choose encrypted communication over RPC = when talking to core hadoop components. Today, the properties that control = this are: - {{core-site.xml : hadoop.rpc.protection =3D authentication}} - {{hdfs-site.xml : dfs.data.transfer.protection =3D authentication}} The new value of=C2=A0{{privacy}}=C2=A0enables clients to choose an encrypt= ed means of communication. By keeping=C2=A0{{authentication}}=C2=A0first, i= t will be taken as the default mechanism so that wire encryption is not aut= omatically enabled by accident. The following properties should be changed to add=C2=A0{{privacy}}: - {{core-site.xml : hadoop.rpc.protection =3D authentication,privacy}} - {{hdfs-site.xml : dfs.data.transfer.protection =3D authentication,privac= y}} The following are cases when this needs to be performed: - During Kerberization, the above two properties should be automatically r= econfigured. - During a stack upgrade to any version of HDP 2.6, they should be automat= ically merged Blueprint deployment is not a scenario being covered here. > Update Hadoop RPC Encryption Properties During Kerberization and Upgrade > ------------------------------------------------------------------------ > > Key: AMBARI-22803 > URL: https://issues.apache.org/jira/browse/AMBARI-22803 > Project: Ambari > Issue Type: Task > Components: ambari-server > Affects Versions: 2.7.0 > Reporter: Jonathan Hurley > Assignee: Robert Levas > Priority: Critical > Fix For: 2.7.0 > > > When *HDP 3.0.0* is installed, clients should have the ability to choose = encrypted communication over RPC when talking to core hadoop components. To= day, the properties that control this are: > - {{core-site.xml : hadoop.rpc.protection =3D authentication}} > - {{hdfs-site.xml : dfs.data.transfer.protection =3D authentication}} > The new value of=C2=A0{{privacy}}=C2=A0enables clients to choose an encry= pted means of communication. By keeping=C2=A0{{authentication}}=C2=A0first,= it will be taken as the default mechanism so that wire encryption is not a= utomatically enabled by accident. > The following properties should be changed to add=C2=A0{{privacy}}: > - {{core-site.xml : hadoop.rpc.protection =3D authentication,privacy}} > - {{hdfs-site.xml : dfs.data.transfer.protection =3D authentication,priv= acy}} > The following are cases when this needs to be performed: > - During Kerberization, the above two properties should be automatically= reconfigured. > - During a stack upgrade to any version of HDP 2.6, they should be autom= atically merged > Blueprint deployment is not a scenario being covered here. -- This message was sent by Atlassian JIRA (v7.6.3#76005)