AMBARI-21477: Remove Falcon proxy entries from Knox kerberos.json (dili)

Project: http://git-wip-us.apache.org/repos/asf/ambari/repo
Commit: http://git-wip-us.apache.org/repos/asf/ambari/commit/ec3cf228
Tree: http://git-wip-us.apache.org/repos/asf/ambari/tree/ec3cf228
Diff: http://git-wip-us.apache.org/repos/asf/ambari/diff/ec3cf228

Branch: refs/heads/branch-feature-AMBARI-21348
Commit: ec3cf228542f6d9c41ef63c119dd9284d4d19acf
Parents: 9f0bba6
Author: Di Li <[email protected]>
Authored: Fri Jul 14 14:22:18 2017 -0400
Committer: Di Li <[email protected]>
Committed: Fri Jul 14 14:22:18 2017 -0400

----------------------------------------------------------------------
 .../stacks/BigInsights/4.2/services/KNOX/kerberos.json         | 6 ------
 1 file changed, 6 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/ambari/blob/ec3cf228/ambari-server/src/main/resources/stacks/BigInsights/4.2/services/KNOX/kerberos.json
----------------------------------------------------------------------
diff --git 
a/ambari-server/src/main/resources/stacks/BigInsights/4.2/services/KNOX/kerberos.json
 
b/ambari-server/src/main/resources/stacks/BigInsights/4.2/services/KNOX/kerberos.json
index 8ee2acc..6a89af6 100755
--- 
a/ambari-server/src/main/resources/stacks/BigInsights/4.2/services/KNOX/kerberos.json
+++ 
b/ambari-server/src/main/resources/stacks/BigInsights/4.2/services/KNOX/kerberos.json
@@ -53,12 +53,6 @@
                 
"oozie.service.ProxyUserService.proxyuser.${knox-env/knox_user}.groups": 
"${hadoop-env/proxyuser_group}",
                 
"oozie.service.ProxyUserService.proxyuser.${knox-env/knox_user}.hosts": 
"${clusterHostInfo/knox_gateway_hosts}"
               }
-            },
-            {
-              "falcon-runtime.properties": {
-                "*.falcon.service.ProxyUserService.proxyuser.knox.groups": 
"${hadoop-env/proxyuser_group}",
-                "*.falcon.service.ProxyUserService.proxyuser.knox.hosts": 
"${host}"
-              }
             }
           ]
         }

Reply via email to