There are cases where a Metadata Aggregate contains attribute isRequired=true/false signalling that if an attribute has isRequired=true, it would be valuable for ADFSToolkit to automatically write the attribute release policy for it.
From a feature perspective it would have the following characteristics:
- be an on/off designation per aggregate
- when isRequired=true is observed it should create the release transform
- settings/behaviour needs more precision on what should happen is an attribute is requested but doesn't exist and may require subsequent settings
Note that this feature pivots the autonomy from IdPs controlling their release policies to that of the Metadata publisher and should be thought about carefully as it is a significant trust model change from regular behaviour
There are cases where a Metadata Aggregate contains attribute isRequired=true/false signalling that if an attribute has isRequired=true, it would be valuable for ADFSToolkit to automatically write the attribute release policy for it.
From a feature perspective it would have the following characteristics:
Note that this feature pivots the autonomy from IdPs controlling their release policies to that of the Metadata publisher and should be thought about carefully as it is a significant trust model change from regular behaviour