IdStory Identity Manager

This is still an issue.

Create VS, by default there is "rights" attribute with merge strategy.
Create some other role with mapping to this system and override "rights" attribute with different strategy then merge => Everything is saved no message is shown.

There is supposed to be check for this during provisioning, but the check is not working right now. The issue is that in parenAttribute is the overridden so checking by merge strategy is not working, because the strategy is SET or whatever you picked.

Firstly I'll fix this issue on BE during provisioning.
Then I'll look if there is some easy way how to prevent saving attribute with conflict strategy

Implementation in https://github.com/bcvsolutions/CzechIdMng/tree/kucerar/1362-conflict-mapping-strategy
Validation was already there, but the way how it was write could never work (conditions were true, because attribute had different strategy then merge)
Now we are directly comparing attributes with overloaded attributes a checking strategies.

I tested it and works nicely. The result is that event end with error and on detail you can see the message that strategies are in conflict.

Next, I will look for some validation on FE.

Strategy select is on role detail system tab is read only, so user will not be able to change the strategy to non compatible one.

PR https://github.com/bcvsolutions/CzechIdMng/pull/225

@doischert Can you do a review please?

This works well but after some consultation and the presentation, it could lead to some issues.

If you have a conflicting strategy now or if you change the strategy in the mapping, you wouldn't be able to change it in the future.

Mapping is not Eventable so a processor cannot be used, so we will create a small LRT that will check sys_role_system_attributes and set the strategy according to the system mapping. (Or maybe we will come up with something better.)

Events are implemented.
LRT is implemented for changing strategy for one or more attributes base on system attribute mapping strategy.
LRT is called from update processor. Processor was called two times, because the update of roleAttribute perform save of mappingAttribute. This is solved by conditional method in processor.

Rebased onto current develop.
Github action still in progress.
https://github.com/bcvsolutions/CzechIdMng/pull/225

@doischert can you do a review please?
https://github.com/bcvsolutions/CzechIdMng/pull/225

It looks good and it works well. I just noticed that localization is missing, see the PR.

@doischert thx, localization added.

LGTM, merged to develop.