Skip to content

[EPIC] Metadata Authorization #6762

Open
@xunliu

Description

@xunliu

Background

The Gravitino implementation permission pushdown underlying data source to authorization (Just like Apache Ranger, IAM, etc.,), Because every data source has a different permissions system, This way lets us difficulty unified authentication, So we consider the implementation a unified metadata authentication in the Gravitino API services.

Advantages

Provider unified metadata authentication in the Gravitino RESTful interface, support curl command and Gravitino Java/Python client to connect Gravitino check authentication based on the user identity.
The Gravitino RESTful interface supports GET/POST/PUT/DELETE operations. These operations map metadata Get a metadata/Create a metadata/Update a metadata/Delete a metadata.

Disadvantages

We are through the RESTful interface only checking authentication metadata permission, Not checking data permission.

Task list

Metadata

Metadata

Labels

epicKey feature

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions