Task #604
closed
MERGE strategy does not remove duplicities
Added by Marcel Poul over 7 years ago.
Updated over 6 years ago.
Description
We use MERGE strategy on LDAP roles. Provisioning queue for the user has same value of the ROLE attribute multiple times.
Merge should remove duplicities on values.
our LDAP can handle this correctly, but we cannot count on that behaviour in general. There might be and I think are systems e.g. DBs that would not handle it that well.
- Target version deleted (
Diamond (7.4.0))
- Priority changed from Normal to High
Came across the situation that LDAP does not handle it.
Alena also checked CzechIdM 6 and there is remove duplicities method called on Merge.
- Target version set to Hematite (8.0.0)
- Assignee changed from Vít Švanda to Ondřej Kopr
I will implement simply check for duplicity in final list.
- Status changed from New to Needs feedback
- Assignee changed from Ondřej Kopr to Vít Švanda
- Priority changed from High to Normal
- % Done changed from 0 to 90
- Status changed from Needs feedback to Resolved
- Assignee changed from Vít Švanda to Ondřej Kopr
- % Done changed from 90 to 100
I did reveiw, and works fine. Documentation and tests are nice too.
- Status changed from Resolved to Closed
Also available in: Atom
PDF
