Title: #21: IFP: expose user and group unique IDs through DBus
On 09/19/2016 02:26 PM, tequeter wrote:
> Yes, I considered creating a |group_attributes| instead. However it
> would have taken more refactoring to avoid duplicating the
> |user_attributes| code than I was comfortable with for a first contribution.
> I went for uniqueID (GUID) instead of SIDs for three reasons:
> * |uniqueID| has a meaningful value both in IPA and AD, so it'll be
> useful to more users.
> * SIDs can change over time in multi-domain configurations.
> * GUIDs are supposedly world-unique, while SIDs can collide in forest
I think we can accept this patch.
user_attributes is meant mostly for custom attributes that are not
downloaded by sssd by default and sssd is not aware of their content.
Since this attribute is managed by sssd it is better to have control
over it by publishing it directly.
It is also useful to have access to SID/GUID since it is far better
concept than UNIX ID and we should make it easily accessible for
See the full comment at
sssd-devel mailing list -- email@example.com
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org