Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[Subtask] Support Kerberos client authentication in gvfs #2711

Closed
Tracked by #2301
xloya opened this issue Mar 28, 2024 · 0 comments · Fixed by #3314
Closed
Tracked by #2301

[Subtask] Support Kerberos client authentication in gvfs #2711

xloya opened this issue Mar 28, 2024 · 0 comments · Fixed by #3314
Assignees
@xloya
Labels
subtask Subtasks of umbrella issue
Milestone
Gravitino June Re...

Comments

@xloya
Copy link
Contributor

xloya commented Mar 28, 2024

Describe the subtask

Support connecting Gravitino Server through Kerberos in gvfs.

Parent issue

#2301
@xloya xloya added the subtask Subtasks of umbrella issue label Mar 28, 2024
@xloya xloya mentioned this issue Mar 28, 2024
Closed
2 tasks
@xloya xloya changed the title [Subtask] Support Kerberos authentication in gvfs [Subtask] Support Kerberos client authentication in gvfs Mar 28, 2024
@jerryshao jerryshao added this to the Gravitino 0.5.0 milestone Apr 1, 2024
@jerryshao jerryshao removed this from the Gravitino 0.5.0 milestone Apr 16, 2024
@jerryshao jerryshao added this to the Gravitino June Release milestone Apr 24, 2024
@xloya xloya mentioned this issue May 9, 2024
Merged
jerryshao pushed a commit that referenced this issue May 11, 2024
@xloya
[#2711] feat(filesystem): Support Kerberos client authentication in g…
77144d7 
…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.

![image](https://github.com/datastrato/gravitino/assets/26177232/f655e687-8412-4000-bb07-bd9ccadd8387)

![image](https://github.com/datastrato/gravitino/assets/26177232/a3d36646-37ad-44b9-8cca-129a18196663)

![image](https://github.com/datastrato/gravitino/assets/26177232/df7504a2-046d-45fa-9da3-7b681ebfd7e1)

---------

Co-authored-by: xiaojiebao <xiaojiebao@xiaomi.com>
github-actions bot pushed a commit that referenced this issue May 11, 2024
@xloya @web-flow
[#2711] feat(filesystem): Support Kerberos client authentication in g…
3e4c1bb 
…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.

![image](https://github.com/datastrato/gravitino/assets/26177232/f655e687-8412-4000-bb07-bd9ccadd8387)

![image](https://github.com/datastrato/gravitino/assets/26177232/a3d36646-37ad-44b9-8cca-129a18196663)

![image](https://github.com/datastrato/gravitino/assets/26177232/df7504a2-046d-45fa-9da3-7b681ebfd7e1)

---------

Co-authored-by: xiaojiebao <xiaojiebao@xiaomi.com>
@jerryshao jerryshao mentioned this issue May 11, 2024
Merged
qqqttt123 pushed a commit that referenced this issue May 11, 2024
@jerryshao @xloya
[#2711] feat(filesystem): Support Kerberos client authentication in g…
636a43e 
…vfs (#3340)

### 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.

![image](https://github.com/datastrato/gravitino/assets/26177232/f655e687-8412-4000-bb07-bd9ccadd8387)

![image](https://github.com/datastrato/gravitino/assets/26177232/a3d36646-37ad-44b9-8cca-129a18196663)

![image](https://github.com/datastrato/gravitino/assets/26177232/df7504a2-046d-45fa-9da3-7b681ebfd7e1)

Co-authored-by: xloya <982052490@qq.com>
Co-authored-by: xiaojiebao <xiaojiebao@xiaomi.com>
diqiu50 pushed a commit to diqiu50/gravitino that referenced this issue Jun 13, 2024
@xloya @diqiu50
[apache#2711] feat(filesystem): Support Kerberos client authenticatio…
8fce3c7 
…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.

![image](https://github.com/datastrato/gravitino/assets/26177232/f655e687-8412-4000-bb07-bd9ccadd8387)

![image](https://github.com/datastrato/gravitino/assets/26177232/a3d36646-37ad-44b9-8cca-129a18196663)

![image](https://github.com/datastrato/gravitino/assets/26177232/df7504a2-046d-45fa-9da3-7b681ebfd7e1)

---------

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
Assignees

@xloya xloya

Labels
subtask Subtasks of umbrella issue
Projects
None yet
Milestone
Gravitino June Release
Development

Successfully merging a pull request may close this issue.

[#2711] feat(filesystem): Support Kerberos client authentication in gvfs xloya/gravitino
2 participants
@jerryshao @xloya