We have an application with 2 different attributes representing entitlements. These entitlements are hierarchical in nature and for some of the applications, there are only certain combinations of group value vs role value.
What is the best way to model the connector in such scenarios? Is concatenation of attributes and combining them into entitlements only way to deal with this? In such cases, how do you manage entitlement aggregation?
Ex:-
Let us consider group as entitlement attribute-1 and role as entitlement attribute-2, you can have multiple roles inside a group.
We have considered permission objects initially, however, below post suggests that permissions are not actively considered to be in SailPoint IIQ’s roadmap.
Solved: Bundle profiles: Attribute rules vs. Permissions - Compass (sailpoint.com)
Eventhough connector type may not have direct impact on object model, any webservices connector specific inputs will be much appreciated.