[#2711] feat(filesystem): Support Kerberos client authentication in gvfs #3314
Conversation
This file contains 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
added 2 commits
May 9, 2024 19:35
|
@qqqttt123 When I write a unit test that only configures the |
|
You should use host name instead of ip. |
You should provide more error information. |
If I use |
The test like this: I wiil get this error: |
|
Oh. I got it. You can't test the ticket cache in the UT. It can only be tested by hand. |
Got it, I'll test it locally. |
xloya
commented
May 10, 2024
docs/how-to-use-gvfs.md
Outdated
| | `fs.gravitino.client.oauth2.credential` | The auth credential for the Gravitino client when using `oauth2` auth type in the Gravitino Virtual File System. | (none) | Yes if you use `oauth2` auth type | 0.5.0 | | ||
| | `fs.gravitino.client.oauth2.path` | The auth server path for the Gravitino client when using `oauth2` auth type with the Gravitino Virtual File System. Please remove the first slash `/` from the path, for example `oauth/token`. | (none) | Yes if you use `oauth2` auth type | 0.5.0 | | ||
| | `fs.gravitino.client.oauth2.scope` | The auth scope for the Gravitino client when using `oauth2` auth type with the Gravitino Virtual File System. | (none) | Yes if you use `oauth2` auth type | 0.5.0 | | ||
| | `fs.gravitino.client.kerberos.principal` | The auth principal for the Gravitino client when using `kerberos` auth type with the Gravitino Virtual File System. | (none) | Yes if you use `kerberos` auth type | 0.5.1 | |
There was a problem hiding this comment.
@jerryshao Do we need backport this pr to branch-0.5? My initial thought is to release it in 0.5.1.
@qqqttt123 I pulled up the KDC Docker image locally and registered |
You should add these to the segment |
qqqttt123
reviewed
May 10, 2024
qqqttt123
reviewed
May 10, 2024
Done |
qqqttt123
approved these changes
May 11, 2024
github-actions bot
pushed a commit
that referenced
this pull request
May 11, 2024
…vfs (#3314) ### What changes were proposed in this pull request? Support using Kerberos authentication type to initialize Gravitino client in gvfs. ### Why are the changes needed? Fix: #2711 ### How was this patch tested? Add some uts for: 1. use principal and keytab to auth. 2. kerberos configs for gvfs. 3. some invalid kerberos case. Test locally and use `kerberos ticket cache` to initialize gvfs. The steps are as follows: 1. Deploy the KDC server locally, refer to the doc: https://blog.csdn.net/lo085213/article/details/105057186. 2. Register the service account `HTTP/localhost@HADOOP.COM` and client account `client@HADOOP.COM` in the KDC server. 3. Execute the `kinit -kt client.keytab client@HADOOP.COM` command locally. 4. Use the `klist` command to check the environment for tickets containing `client@HADOOP.COM`. 5. Write a unit test to load metalake through gvfs with the kerberos ticket cache.    --------- Co-authored-by: xiaojiebao <xiaojiebao@xiaomi.com>
diqiu50
pushed a commit
to diqiu50/gravitino
that referenced
this pull request
Jun 13, 2024
…n in gvfs (apache#3314) ### What changes were proposed in this pull request? Support using Kerberos authentication type to initialize Gravitino client in gvfs. ### Why are the changes needed? Fix: apache#2711 ### How was this patch tested? Add some uts for: 1. use principal and keytab to auth. 2. kerberos configs for gvfs. 3. some invalid kerberos case. Test locally and use `kerberos ticket cache` to initialize gvfs. The steps are as follows: 1. Deploy the KDC server locally, refer to the doc: https://blog.csdn.net/lo085213/article/details/105057186. 2. Register the service account `HTTP/localhost@HADOOP.COM` and client account `client@HADOOP.COM` in the KDC server. 3. Execute the `kinit -kt client.keytab client@HADOOP.COM` command locally. 4. Use the `klist` command to check the environment for tickets containing `client@HADOOP.COM`. 5. Write a unit test to load metalake through gvfs with the kerberos ticket cache.    --------- Co-authored-by: xiaojiebao <xiaojiebao@xiaomi.com>
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.
What changes were proposed in this pull request?
Support using Kerberos authentication type to initialize Gravitino client in gvfs.
Why are the changes needed?
Fix: #2711
How was this patch tested?
Add some uts for:
Test locally and use
kerberos ticket cacheto initialize gvfs. The steps are as follows:HTTP/localhost@HADOOP.COMand client accountclient@HADOOP.COMin the KDC server.kinit -kt client.keytab client@HADOOP.COMcommand locally.klistcommand to check the environment for tickets containingclient@HADOOP.COM.