-
Notifications
You must be signed in to change notification settings - Fork 9.1k
HDFS-14668 Support Fuse with Users from multiple Security Realms #1739
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
💔 -1 overall
This message was automatically generated. |
+1 the fix is deployed and verified to work. |
jojochuang
pushed a commit
that referenced
this pull request
Feb 27, 2020
(cherry picked from commit 57aa048)
bilaharith
pushed a commit
to bilaharith/hadoop
that referenced
this pull request
Mar 19, 2020
RogPodge
pushed a commit
to RogPodge/hadoop
that referenced
this pull request
Mar 25, 2020
bentito
pushed a commit
to bentito/hadoop
that referenced
this pull request
Dec 2, 2020
bentito
pushed a commit
to bentito/hadoop
that referenced
this pull request
Dec 3, 2020
jojochuang
pushed a commit
to jojochuang/hadoop
that referenced
this pull request
May 23, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The rationale behind the change is the following:
when a username is specified to the underlying calls of the FileSystem API, that is specified to the Java kerberos layer as a principal name, and if that does not match the principal in the ticket cache, authentication fails on the Java level. This renders FUSE usable in a kerberized environment, if and only if the user's ticket cache contains a principal who's name is matching the name of the OS user used to access the FUSE mount and the realm of the principal is the default realm per the /etc/krb5.conf file. Other cases have worked before the UserGroupInformation changes in HADOOP-9747, and after the change suggested by this PR.
How it was tested:
In a non-kerberized environment after deploying the new compiled binary and mount hdfs via fuse:
In a kerberized environment after deploying the new compiled binary and mount hdfs via fuse:
The tests were running manually, as it requires a multiple realm setup with cross-realm trust, which we cannot emulate in the current test environment.