This is an automated email from the ASF dual-hosted git repository.
jshao pushed a commit to branch branch-0.9
in repository https://gitbox.apache.org/repos/asf/gravitino.git
The following commit(s) were added to refs/heads/branch-0.9 by this push:
new c25d626f46 [MINOR] fix(docs): Fix the document of access control
(#7195)
c25d626f46 is described below
commit c25d626f46ff1df64927f21fff22cfea7137a2fb
Author: github-actions[bot]
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Wed May 21 14:43:58 2025 +0800
[MINOR] fix(docs): Fix the document of access control (#7195)
### What changes were proposed in this pull request?
After discussion, we don't need to switch roles to authenticate, we use
all the roles.
### Why are the changes needed?
Just a minor.
### Does this PR introduce _any_ user-facing change?
No.
### How was this patch tested?
No need.
Co-authored-by: roryqi <[email protected]>
---
docs/security/access-control.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/docs/security/access-control.md b/docs/security/access-control.md
index f2319222f8..0c4cee7842 100644
--- a/docs/security/access-control.md
+++ b/docs/security/access-control.md
@@ -56,7 +56,7 @@ More information you can see the [Authorization push
down](authorization-pushdow
As mentioned above, Gravitino uses Ownership to control the privileges of
securable object in the management category and uses Role to control access
securable objects,
so when a user performs a specific operation on a specified resource,
Gravitino will perform a composite authentication on the Ownership and Role to
which the securable object belongs.
-When a user has more than one Role, Gravitino will use the user's current Role
for authentication, and the user can switch the current Role to access a
different securable object.
+When a user has more than one Role, Gravitino will use the user's all the
Roles for authentication.
### Role
