[midPoint] lifecycleState on user object?

[Radovan Semancik]

Hi,

Yes. It is used for a couple of cases already. E.g. user 
pre-registration and self-registration. Users are created in "proposed" 
state until they are fully activated by user's action. They they are 
switched to "active" state.

Therefore your plan is well aligned with the purpose of lifecycle state 
model that we had in mind when we designed it. However, the 
implementation of full lifecycle model is not complete. The fundamental 
framework is there, basic functionality is supposed to work, but it is 
not yet feature-complete. Therefore it would be a good idea to prototype 
your solution first.

-- 
Radovan Semancik
Software Architect
evolveum.com



On 5/15/19 8:37 PM, Keith Hazelton wrote:
> I see that lifecycleState is often used on role objects. Are there 
> situations where lifecycleState on a user object can be of use?
>
> The case I'm thinking of is we want to keep a user in proposed 
> lifecycle state until midPoint has information on the user from all 
> the required line of business systems.
>
>      Thanks in advance for any ideas,   --Keith Hazelton
>
> __________
>
> hazelton at internet2.edu
>
>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.evolveum.com/pipermail/midpoint/attachments/20190516/fb924c16/attachment.htm>