Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
devel:documentation:security:dev:change-user-permissions [2019/01/30 09:31] svandav [Approval by the security department] |
devel:documentation:security:dev:change-user-permissions [2019/05/07 08:29] (current) svandav [Duplicate request] |
||
---|---|---|---|
Line 1: | Line 1: | ||
====== Changing user permissions ====== | ====== Changing user permissions ====== | ||
- | {{tag> | + | {{tag> |
<note tip> | <note tip> | ||
- | A manual change (via REST api) of permission, i.e. adding/ | + | |
+ | ===== Basic life cycle of the request for change a permissions ===== | ||
+ | |||
+ | {{: | ||
+ | |||
+ | <note important> | ||
===== Role request agenda ===== | ===== Role request agenda ===== | ||
Line 25: | Line 30: | ||
<note tip>If the user creates a new request but does not submit it, it will be displayed as " | <note tip>If the user creates a new request but does not submit it, it will be displayed as " | ||
- | |||
- | {{: | ||
- | |||
=== Concept table === | === Concept table === | ||
Line 38: | Line 40: | ||
<note important> | <note important> | ||
- | |||
- | {{: | ||
==== Changing permission without approval ==== | ==== Changing permission without approval ==== | ||
Line 57: | Line 57: | ||
==== Duplicate request ==== | ==== Duplicate request ==== | ||
+ | <note warning> | ||
+ | |||
During the process of submitting a request, it is verified if there is another duplicate request of the new request (in state " | During the process of submitting a request, it is verified if there is another duplicate request of the new request (in state " | ||
The submission (execution) of the request is thus suspended. | The submission (execution) of the request is thus suspended. | ||
Line 78: | Line 80: | ||
The agenda allows a direct request submission from a list of requests. The agenda also allows **creating a new request**, where the administrator must first choose the user who the request is being created for. | The agenda allows a direct request submission from a list of requests. The agenda also allows **creating a new request**, where the administrator must first choose the user who the request is being created for. | ||
- | |||
- | {{: | ||
In addition, the request detail in this agenda contains (compared to the end user request detail) a possibility of ticking that the request is not to be approved. The request detail also contains a **log**. This log contains all crucial information which occur during the life cycle of the request (errors, duplicates, request cancellation due to integrity, executed operations, etc.). | In addition, the request detail in this agenda contains (compared to the end user request detail) a possibility of ticking that the request is not to be approved. The request detail also contains a **log**. This log contains all crucial information which occur during the life cycle of the request (errors, duplicates, request cancellation due to integrity, executed operations, etc.). | ||
- | |||
- | {{: | ||
==== Integrity on remove contract or role ==== | ==== Integrity on remove contract or role ==== | ||
Line 213: | Line 211: | ||
* **No priority (0)**: | * **No priority (0)**: | ||
- | No approval takes place. The process " | + | No approval takes place. The process " |
* **Trivial priority (1)**: | * **Trivial priority (1)**: |