From d9c9e67687cf7d372662e156a6f8a48f1396c615 Mon Sep 17 00:00:00 2001 From: Faustin Date: Mon, 2 Dec 2024 17:09:24 +0100 Subject: [PATCH] fix: lint --- .docs/content/1.concepts/3.authentication.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/.docs/content/1.concepts/3.authentication.md b/.docs/content/1.concepts/3.authentication.md index 20e4aad77..d9065c4bf 100644 --- a/.docs/content/1.concepts/3.authentication.md +++ b/.docs/content/1.concepts/3.authentication.md @@ -23,9 +23,10 @@ ArmoniK allows users to impersonate other users by adding an impersonation heade ArmoniK uses a User-Role-Permission based approach to handle authorization. Each user in the database can have a set of **Roles**. Each role contains a set of **Permissions**. A user cannot receive permissions directly, instead roles containing the permissions have to be created and given to the user. A permission is defined as a string in a specific format. The current version handles the following types of permissions : + |Format|Example|Parameters|Description| ----|---|---|---| -``General:Impersonate:``|``General:Impersonate:Monitoring``|**Rolename**: Name of a role|Grants the right to impersonate a user with the role named \. See [Impersonation](#impersonation) for details| +|---|---|---|---| +|``General:Impersonate:``|``General:Impersonate:Monitoring``|**Rolename**: Name of a role|Grants the right to impersonate a user with the role named \. See [Impersonation](#impersonation) for details| |``:``|``Submitter:CreateSession``|**Service**: Name of an ArmoniK web service
**Name**: Name of the endpoint|Grants the right to use the endpoint named \ of the service named \| |``::``|``Submitter:CancelSession:Self``|**Service**: Name of an ArmoniK web service
**Name**: Name of the endpoint
**Target**: Target or scope of the permission|Same as ``:`` as ```` is currently unused|