Details
-
Improvement
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
None
-
None
-
None
Description
Update consistency mechanism to 21.century standards. It was not reviewed for some time.
Things to address:
- What to do if reading of full account fails? Can we process all the mappings reliably? E.g. what to do with weak and strong mappings?
- Prepare the design for attribute caching.
Attachments
Issue Links
- relates to
-
MID-4542 Unify pendingOperation and consistency mechanism
-
- Closed
-
-
MID-2087 Provisioning + consistency + strict dependencies problem
-
- Open
-
-
MID-1518 Notifications on retried account operations may contain wrong or empty REQUESTER information
-
- Open
-
-
MID-1748 Editing user details for user with unreachable resource throws exception when saving, although no attributes are being pushed to that resource
-
- Resolved
-
-
MID-3466 Error when trying to show the result for the shadow
-
- Resolved
-
-
MID-3604 Shadow object exists in the mp with no owner but with situation=LINKED
-
- Resolved
-
-
MID-3774 consequence of ObjectAlreadyExistsException on target system is not created user in MP when we try to import from HR source
-
- Resolved
-
-
MID-3778 Results of "discovery" operation are not correctly integrated into main operation
-
- Resolved
-
-
MID-2174 After successful execution of postponed modify operation the objectChange remains in the shadow
-
- Closed
-
-
MID-3110 red message box after success exception handling
-
- Closed
-
-
MID-3842 Getting shadow/account in GUI should not try to apply roles etc.
-
- Closed
-
-
MID-4038 Deleting user does not delete situation from source system shadow
-
- Closed
-
-
MID-1094 Notify failure
-
- Open
-
-
MID-4073 Cleanup task (part 2)
-
- Open
-
-
MID-3353 Consistency mechanism tests cleanup
-
- Open
-
-
MID-2557 Clean up ResourceObjectChangeListener and ResourceEventListener
-
- Open
-
-
MID-2829 Clean up ShadowManager
-
- Open
-
-
MID-4833 Proposed shadow cleanup
-
- Resolved
-
-
MID-4780 Remove legacy consistency properties from schema
-
- Closed
-
-
MID-4490 Merging conflicting shadows
-
- Open
-
-
MID-4056 Shadow objects don't have creatorRef, creationTimestamp, only modifications
-
- Open
-
-
MID-4330 Consistency user experience: repeated message
-
- Open
-
-
MID-4787 Support scripts in retried (postponed) operations
-
- Open
-
-
MID-4796 Implement proper behavior of staleness=0 in provisioning
-
- Open
-
-
MID-4824 Clean up ContextLoader
-
- Open
-
-
MID-1484 Synchronization and DELETED situation
-
- Reopened
-
-
MID-2275 Display infor about incomplete operations in shadow
-
- Resolved
-
-
MID-3561 not actual FailedOperationTypeType.null:Partial Error in Shadow Result on Accounts->Repository page
-
- Resolved
-
-
MID-4389 Shadow FailedOperation retry
-
- Resolved
-
-
MID-3115 Consistency, model and shadow graveyard
-
- Closed
-
-
MID-1200 Cleanup task
-
- Closed
-
-
MID-1566 Dependencies and consistency
-
- Closed
-
-
MID-3891 Thombstone (dead shadow) expiration
-
- Closed
-
-
MID-1085 Adding, Deleting already existing account on dead resource generates reconciliation errors.
-
- Closed
-
- mentioned in
-
Page Loading...