[midPoint] Creating delegations through mapping

[Jan Vaňáček - AMI Praha a.s.]

1) to make it more robust - delegations concerns delegator and deputy and
data are saved just in deputy object. So e.g. ServiceType object can be
easily searched. And I think it would be more difficult to directly edit
assignment container (we just separated "synchronization of attributes" part
and "creating of delegations" part). And we did it mainly from historic
reason because we used similar concept with sth different.
2) we use native delegations
3) it is a simple:

You just need to fill assignment with all required data.

propDeltas.add(ContainerDelta.createModificationAdd(UserType.F_ASSIGNMENT,
UserType.class, midpoint.getPrismContext(), assignment));
modifyTypeDelta = ObjectDelta.createModifyDelta(deputy.oid, propDeltas,
UserType.class, midpoint.getPrismContext());
midpoint.executeChanges(modifyTypeDelta);

JAVA

-----Original Message-----
From: midPoint <midpoint-bounces at lists.evolveum.com> On Behalf Of Peter
Holes
Sent: Thursday, January 23, 2020 9:56 PM
To: midpoint at lists.evolveum.com
Subject: Re: [midPoint] Creating delegations through mapping

Hi Jan,
Thanks for your quick answer. Regarding your concept, I have a couple of
additional questions:

1.) Why do you create a ServiceType object and not create assignment
container with delegation direct on user? The only thought that come into my
mind is to store additional attributes and store multiple delegation onto
one midPoint object. Benefit of such concept is to simplifying management of
big amount of delegations.
2.) Or you are using ServiceTypes as a "custom delegation object"
instead of native midPoint functionality?
3.) In case you're using native midPoint delegations, can you share small
example, how to correctly create a assignment container with delegation
definition ?

Thanks
Peter.
_______________________________________________
midPoint mailing list
midPoint at lists.evolveum.com
http://lists.evolveum.com/mailman/listinfo/midpoint