From 317680ba24ddb70eb6d198164c1cf571a5b0d7b4 Mon Sep 17 00:00:00 2001 From: Istvan Fajth Date: Fri, 6 Dec 2019 13:24:14 +0100 Subject: [PATCH] HDFS-14668 Support Fuse with Users from multiple Security Realms --- .../src/main/native/fuse-dfs/fuse_connect.c | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/fuse-dfs/fuse_connect.c b/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/fuse-dfs/fuse_connect.c index f08917a53c15d..103ed4e626e5c 100644 --- a/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/fuse-dfs/fuse_connect.c +++ b/hadoop-hdfs-project/hadoop-hdfs-native-client/src/main/native/fuse-dfs/fuse_connect.c @@ -476,7 +476,6 @@ static int fuseNewConnect(const char *usrname, struct fuse_context *ctx, if (gPort) { hdfsBuilderSetNameNodePort(bld, gPort); } - hdfsBuilderSetUserName(bld, usrname); if (gHdfsAuthConf == AUTH_CONF_KERBEROS) { findKerbTicketCachePath(ctx, kpath, sizeof(kpath)); if (stat(kpath, &st) < 0) { @@ -495,6 +494,17 @@ static int fuseNewConnect(const char *usrname, struct fuse_context *ctx, ret = -ENOMEM; goto error; } + } else { + // earlier the username was set to the builder always, but due to + // HADOOP-9747 if we specify the username in case of kerberos authentication + // the username will be used as the principal name, and that will conflict + // with ticket cache based authentication as we have the OS user name here + // not the real kerberos principal name. So with SIMPLE auth we pass on the + // OS username still, and the UGI will use that as the username, but with + // kerberos authentication we do not pass in the OS username and let the + // authentication happen with the principal who's ticket is in the ticket + // cache. (HDFS-15034 is still a possible improvement for SIMPLE AUTH.) + hdfsBuilderSetUserName(bld, usrname); } conn->usrname = strdup(usrname); if (!conn->usrname) {