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/23 09:04] svandav [Failed state] |
devel:documentation:roles:adm:role_assignment [2019/07/29 11:48] svandav [Notification] |
||
---|---|---|---|
Line 90: | Line 90: | ||
====== System state ====== | ====== 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**. | 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**. | ||
Line 98: | Line 100: | ||
==== Running state ==== | ==== Running state ==== | ||
+ | {{tag> | ||
Some of the provisioning operations is not completed. | Some of the provisioning operations is not completed. | ||
Line 104: | Line 107: | ||
{{ : | {{ : | ||
+ | |||
+ | **Second** situation when could be request in running state is if role assign **the virtual system**. | ||
+ | |||
+ | If the request assign or changes an account on the virtual system, then the virtual system creates a request by default, pending implementation by the appropriate implementer. Our request to change roles will be in a running state until all possible requests on virtual systems are resolved. The purpose of this wait is to ensure that the final notification of the completion of the request is sent after the real implementation of the requirements on the systems representing the virtual systems. | ||
+ | |||
+ | 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 ==== | ==== Failed state ==== | ||
- | Some of the provisioning operations failed. | + | 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**. | 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**. | ||
{{ : | {{ : | ||
Line 122: | Line 139: | ||
{{ : | {{ : | ||
+ | |||
+ | ==== 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 agenda**, all operations that were created under a given request have a link to that request (**key icon**). | **In the provisioning operations agenda**, all operations that were created under a given request have a link to that request (**key icon**). | ||
{{ : | {{ : | ||
+ | |||
+ | **Similarly in the agenda of virtual system' | ||
+ | |||
+ | {{ : | ||
===== Notification ===== | ===== Notification ===== | ||
+ | **These notifications are sent when the application is fully completed.** | ||
+ | |||
+ | <note important> | ||
+ | |||
+ | **Two notifications** are sent, one to the author of the request and the other to whom the request changes permissions. The notification contains a list of all directly changed roles (ie does not include business roles). Roles are displayed in three tables according to the type of operation they performed with the role (assignment, | ||
+ | |||
+ | The notification also contains a column " | ||
+ | |||
+ | |||
+ | <note tip>The notification includes a ** link ** to the detail of the relevant IdM role change request.</ | ||
+ | |||
+ | {{ : | ||
+ | |||
+ | **Name of email templates**: | ||
+ | * ``changeIdentityRoleImplementer`` | ||
+ | * ``changeIdentityRole`` | ||
+ | |||
+ | < | ||
+ | |||
+ | <note warning> | ||
+ | |||
+ | **Name of topics**: | ||
+ | * ``core: | ||
+ | * ``core: | ||
+ | |||
+ | <note warning> | ||
- | {{ : | ||