[midPoint] intent filter/expression?

[Radovan Semancik]

Hi,

Understood. The idea of "index" was also inspired by a similar use case 
(labs/sites/domains). But that needs a subscription to get implemented.

Also for resources: from time ti time there is a request to support 
"multi-resource". Which means several resources that have (almost) the 
same configuration, just some details are different (e.g. hostname). 
This is also possible to implement. But again, subscription is needed.

-- 
Radovan Semancik
Software Architect
evolveum.com



On 12/06/2017 11:03 AM, Wojciech Staszewski wrote:
> Thanks both of you.
>
> At least I know what to do now, how to create the roles and that my tries was a waste of time.
> The idea of intents is great (normal/admin/testing accounts), but sometimes, in my case for example,
> it can be up to 8 intents in one resource for 8 remote labs and 1 user can have 8 accounts for normal work.
> So I have to setup 8x more of everything.
> I wonder if it will be easier to multiply resources, eg. have 8 resources, each for different account intent (remote lab) so every intent will be "default" then.
>
> Best regards!
> WS
>
> W dniu 06.12.2017 o 10:05, Radovan Semancik pisze:
>> Hi,
>>
>> Yes, kind/intent is fixed. And, strictly speaking it has to remain fixed because resource+kind+intent triple determines object type, which determines the schema (and some policies). That is how midPoint is implemented now.
>>
>> But, despite that, there are places where we do not need to be that strict. Theoretically intent could be determined dynamically at some places in the future. But there may be limitations (e.g. resource wizard will not work properly). And this is going to make the code a bit more complex than it is now. Therefore we will do that only if there is funding for development of this feature and funding for maintenance as well (i.e. platform subscription is needed).
>>
>> We are also thinking about alternative feature. We would like to add "index" as a new element to existing resource+kind+intent triple. The idea is that resource+kind+intent would completely define the schema and policies. And then "index" could be dynamically managed and it would define an "instance", "site", "domain", "realm" and so on. That way we can get both "formal correctness" and dynamics. But this feature is not yet implemented and not even planned for any midPoint versions in a near
>> future. Platfrom subscription is needed for this as well.
>>
> _______________________________________________
> midPoint mailing list
> midPoint at lists.evolveum.com
> http://lists.evolveum.com/mailman/listinfo/midpoint