Task #765
closed
Virtual systems: add new attribute invokes empty task
Added by Marcel Poul about 7 years ago.
Updated about 7 years ago.
Description
When I add new attribute to System schema mapping for virtual system e.b. System 1, CzechIdM creates task with new attribute but no change in its detail (change is new attribute without value). Actually it happens after I save the identity with account on the virtual system, so relatively randomly.
From my point of view, those tasks should not be created.
Files
- Status changed from New to Needs feedback
- Assignee changed from Vít Švanda to Marcel Poul
Do you have some unresolved (previous/next) VS requests?
Do you have mapped rights attribute? By default it is multivalued attribute withou mapping on entity field (or EAV).
Are same data (none change for rights) in email notification?
Tomorrow we can make call and solve this directly.
Vít Švanda wrote:
Do you have some unresolved (previous/next) VS requests?
yes, many
Do you have mapped rights attribute? By default it is multivalued attribute withou mapping on entity field (or EAV).
I can test for another attribute. I tested on demo and before I corrected it, the attribute was configured wrong. Maybe there was something wrong I will let you know.
Are same data (none change for rights) in email notification?
Tomorrow we can make call and solve this directly.
- Assignee changed from Marcel Poul to Vít Švanda
I was able to replicate the behaviour, but It really seems wierd to me:
Online demo, user Jindřiška, roles: dva systémy, systém 3 user, time: around 20:30 today,
1) I have randomly chosen the user - Jindřiška. She already had roles "dva systémy" assigned since 17:40 (not from me). There already were 2 requests for virtual systems (Systém 1 and Systém 2)
2) I created new Systém 3 as a copy of Systém 2 and enabled it then created role "systém 3 user" with schéma for Systém 3. No attributes overwrited
3) I assigned the user role "systém 3 user" and 3 tasks were created - 2 update operations for system 1 and 2 and one create operation for system 3
4) Then Added new attribute to Systém 3 schéma and provisioning mapping.
5) I saved Jindřiška entity 2 times. No more tasks for virtual systems created
6) I resolved the 3 tasks and resaved Jindřiška
7) Now there are 3 new tasks - those for Systém 1 and 2 has "rights" attribute empty but coloured as changed. Task for systém 3 cannot open, loading forever.
Hope I remember steps well, in all cases there is audit log in the online demo.
There might be corrupted data - it is online demo, but still...
Another usecase:
user: cerhat, online demo
1) gave user cerhat role "dva systémy" - 2 task for create. Both datails has ENABLE attribute empty
2) added new attribute "new_attr_sys_2" to Systém 2 schema and mapping - (with type String - I know it should be java.lang.String)
3) resaved user, no new tasks.
4) resolved tasks and resaved - 2 new tasks. But: with ENABLE = true and rights empty and coloured, no new_attr_sys_2 (because of bad type?)
Systém 2 has the rights attributed filled from "Systém 2 rights" with Authoritative merge strategy.
- Assignee changed from Vít Švanda to Ondřej Kopr
- Target version set to Emerald (7.5.0)
Causes and consequences are now clear.
Problem is not in VS but in provisioning. "Conflict" occures when we have empty list on one side and null on other side.
- This situations (here for 'rights' attirbute) was resolved as different values and provisioning (on the system ) was executed.
I consulted this with Zdeněk. From now (7.5.) we will use this rule in provisioning: Multivalued attribute with null value is equals to value with empty list.
- I this implemented to provisioning.
Task for systém 3 cannot open, loading forever.
I try simulated this, but without success. I added some fix by javascript console on demo enviroment.
Everything are in develop and will be released with version 7.5.0.
Fixed problem with Enable attribute.
- File rights.png rights.png added
- Status changed from Needs feedback to Resolved
- Assignee changed from Ondřej Kopr to Vít Švanda
- % Done changed from 0 to 100
Check rights and now works with multivalued attribute and null values correctly. Also check enable attribute (true => false)
- Status changed from Resolved to Closed
Also available in: Atom
PDF
