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 11:54] svandav [System state] |
devel:documentation:roles:adm:role_assignment [2019/07/29 07:25] tomiskar |
||
---|---|---|---|
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 106: | Line 108: | ||
{{ : | {{ : | ||
- | **Second** situation when could be request in running state is if role assign **the virtula | + | **Second** situation when could be request in running state is if role assign **the virtual |
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. | 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. | ||
Line 114: | Line 116: | ||
{{ : | {{ : | ||
- | If the request contains **pannding virtula | + | If the request contains **pending virtual |
{{ : | {{ : |