Reconciliation
Reconciliation
In this article is described use case for reconciliation, which means that workflows will start based on certain information read from the source system.
Reconciliation is ongoing process in the background and it will start based on scheduled time in provisioning task (scheduled-based provisioning task). It can be also started manually from the configuration console, but please notice that this action will need access to configuration.

Use Case Description
|
Description |
Overview |
This use case describes reconciliation process for reading user and group (entitlement) information from the Customers directory and actions that will take place if IGA solution detects exception between information itself and information read from the directory. |
Operators |
IGA solution |
Prerequisites |
Scheduled-based provisioning task needs to be configured |
Result |
Reconciliation is completed successfully or an IGA Admin Task is created to IGA Admin for manual handling. |
Operating chain |
|
| Auditing Details |
Audit details are saved 1. When exception in user or entitlement data is detected, IGA Access Right Record is created (type read from the directory). 2. When Manager approves approval request IGA Access Right Record is created for approval information and for updating users access rights 3. When Manager rejects approval request, IGA Access Right Record is created for approval information and for updating users access rights. |
Related datacards |
IGA Request |
Delete
Configuration changes
In this use case there are several different settings which can be configured according to Customer needs and they don't have affect to the project schedule or work estimations.
1. In the use case operating chain, step 1, Customer can define three (3) more attributes to be compared
2. In the use case operating chain, in step 2, Customer can choose time limit for approval request waiting before creating IGA Admin Task to IGA Admins
3. In the use case operating chain, in step 3, Customer can choose values for
-
Last login time (appears in several phases, possible to adjust in all of those)
-
Which values are compared for user account attributes
-
User accounts with x entitlement and last login was made x time ago
Delete
Expansion possibilities
1. Customer can request more attributes to be compared, but it will need Matrix42consultant for validating work estimations and affects to the project schedule
2. Customer can request more views and reports, but it will need Matrix42consultant for validating work estimations and affects to the project schedule
3. Customer can request more directories or other integrated applications to be added to de-provisioning process, but it will need Matrix42consultant for validating work estimations and affects to the project schedule
DeleteRelations & configuration instructions
Relations to other use cases,
Relations to other data cards,
IGA Service Request
Approval
IGA Account
IGA Entitlement
IGA Admin Task
Configuration instructions,
- Check Scheduled-based EPEtask called "Reading Data from [Directory] "
- Test connection from the EPEtask
- Check user and group filters and settings
- Check task scheduling
- Check that you have listeners in IGA account template (those will create IGA admin tasks)
- Postsave.De-provisioning [Directory] data diverges from the data stored in IGA(TL230322)
- Postsave.De-provisioning [Directory] data diverges from the data stored in IGA(TL230322)
- Check that you have transform from the IGA Account template to the IGA Admin task

- Test Read account and entitlement data from source directory to ESM
- Check that IGA Accounts are imported to ESM
- Check that IGA Entitlement are imported to ESM
- Change Email Address for user that have identity storage in Directory and check that Admin task is created