Differences
This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
devel:documentation:roles:adm:role_assignment [2019/07/22 12:54] svandav |
devel:documentation:roles:adm:role_assignment [2019/07/29 09:00] svandav [Notification] |
||
---|---|---|---|
Line 74: | Line 74: | ||
<note important> | <note important> | ||
- | ====== The approval process | + | ===== The approval process ===== |
If the request-permission-change-without-approval mode is not used, process " | If the request-permission-change-without-approval mode is not used, process " | ||
Line 89: | Line 89: | ||
- **Realization of the request** - the realization itself is not carried out by the process, but by the service for managing requests for permission change. | - **Realization of the request** - the realization itself is not carried out by the process, but by the service for managing requests for permission change. | ||
- | < | + | ====== System state ====== |
+ | |||
+ | {{tag> | ||
+ | |||
+ | The role request has a status item that identifies whether the request has already been executed. The **Executed** state in this case means that the request has been approved and the changes have been executed in IdM. **This state only reflects the state in IdM**. | ||
+ | |||
+ | This status does not cover a situation where some of the assigned roles create an account on a **system**. In this case, it may be important for the user to know the exact time the **account was successfully created**. Alternatively, | ||
+ | |||
+ | < | ||
+ | |||
+ | ==== Running state ==== | ||
+ | {{tag> | ||
+ | |||
+ | Some of the provisioning operations is not completed. | ||
+ | |||
+ | This is typically a situation where the connector (target system) is waiting to process the operation. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | **Second** situation when could be request in running state is if role assign **the virtual system**. | ||
+ | |||
+ | If the request assign or changes | ||
+ | |||
+ | In this situation has system state **RUNNING** orange color and show message: **Some requests on this vritual systems [Name of vritual systems] are not resloved!**. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | If the request contains **pending virtual system requests**, the ' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== Failed state ==== | ||
+ | |||
+ | Some of the **provisioning operations failed**. | ||
+ | |||
+ | This is typically a situation where the connector throw an exception. If you click on the status, you will see information on **which systems have failed**. | ||
+ | |||
+ | If the request contains an error, the status on the systems will be set to executed only if all errors are resolved. This means that they will either be successfully executed (for example by retry mechanism) or will be canceled. If the operation is canceled, the status on the request item will also be set to **CANCELED**. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | === Detail of failed request === | ||
+ | |||
+ | On the detail of a request that has provisioning errors, the **roles that connect the system to which the error occurred are marked with a specific error**. | ||
+ | |||
+ | If one role assigns more than one system and an error occurs on both, **error for only one system will be displayed**. | ||
+ | |||
+ | If the entire | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== Blocked state ==== | ||
+ | |||
+ | Some of the **provisioning operations were blocked**. | ||
+ | |||
+ | This is typically a situation where some system has blocked write operations. The behavior in this case is very similar to the case when the provisioning operation is in the error. If you click on the status, you will see information **which systems are blocked**. | ||
+ | |||
+ | If the request contains a blocked operations, the status on the systems will be set to executed only if all blocked operations will be resolved. This means that they will either be successfully executed or will be canceled. If the operation is canceled, the status on the request item will also be set to **CANCELED**. | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | ==== Not executed state ==== | ||
+ | This state is **very similar to the case when the provisioning operation is blocked**. Occures where system is seta to **read only** mode. | ||
+ | ===== Link to request ===== | ||
+ | |||
+ | **In the provisioning operations | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | **Similarly in the agenda of virtual system' | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | |||
+ | ===== Notification ===== | ||
+ | |||
+ | {{ : | ||
+ |