Skip to content

Commit

Permalink
[#4754] fix(docs): Optimize the document of access control (#4776)
Browse files Browse the repository at this point in the history
### What changes were proposed in this pull request?

Optimize the document of access control

### Why are the changes needed?

Fix: #4754

### Does this PR introduce _any_ user-facing change?

No.

### How was this patch tested?
Just docs.
  • Loading branch information
jerqi authored Aug 29, 2024
1 parent 8906c03 commit 5295dd9
Showing 1 changed file with 7 additions and 0 deletions.
7 changes: 7 additions & 0 deletions docs/security/access-control.md
Original file line number Diff line number Diff line change
Expand Up @@ -246,6 +246,13 @@ The related configuration is as follows.
| `gravitino.authorization.enable` | Whether Gravitino enable authorization or not. | false | No | 0.5.0 |
| `gravitino.authorization.serviceAdmins` | The admins of Gravitino service, multiple admins are spitted by comma. | (none) | Yes if enables the authorization | 0.5.0 |

:::info

If you enable authorization, you should add users to the metalake first, otherwise you will fail to create metadata objects.
If you don't set a user explicitly, you will use `anonymous` as the user.
When you enable authorization and create a metalake, the service will add the creator to the metalake automatically.

:::

## User Operation

Expand Down

0 comments on commit 5295dd9

Please sign in to comment.