From: Krzysztof B. <kb...@un...> - 2020-08-04 07:56:43
|
Morning Sander, W dniu 03.08.2020 o 08:39, Sander Apweiler pisze: > Good morning Krzysztof, > I agree that identifiers are needed. But is there a possibility to grab > the displayname of a group, e.g. in output translation profile? In this > case we could release the group membership information like the group > administrators and service providers would expect them. > > I'll give you an example. We have a group m-team which is managed by a > group administrator. He created a subgroup feudal-developers and asked > specific service providers to support his group /m-team/feudal- > developers but the service provider only see /m-team/NNE09. > > Having the possibility to access the displayname, we could create a new > attribute containing the expected information. Hmm I wonder whether this is the right path. Shouldn't this be opposite? I.e. on output profile/protocol etc I would rather send 'NNE09' as the identifier and configure all policies around this - this is stable identifier. If you program around displayed name then... who knows what needs to be updated after some upman admin "improves" the displayed name? I agree that giving access to displayed name (also in output profile) makes sense in general, to add some human readable context (useful e.g. for debuggin, initial config) but the base thing for me is the stable identifier. What do you think? KB |