On 12/18/2013 05:37 PM, Jason Voorhees wrote:
> Unfortunately, yes, that's an issue.
>
> The user ID must be a 32bit unsigned integer on a POSIX system. I don't
> see any attribute with the user entry that could be (ab)used as a user
> ID, sorry. I'm afraid one would need to be added on the LDAP side..
I'm sad about that :(
Is there a way to remove the leading 'P' that is leading in the 'uid'
attribute so I can use the numeric value?
_______________________________________________
sssd-users mailing list
sssd-users(a)lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/sssd-users AFAIU since you
can't touch the server you can't do it with the stock SSSD.
I see couple options here:
1) Add custom code to SSSD to transform the select UID into numeric ID.
This should be a generic enough solution to have value for use cases
like this in general to be accepted upstream. Patches welcome!
2) Use custom fix for SSSD and do custom build. This will leave you with
the maintenance overhead but this is for you to decide whether it is
worth it.
3) Setup a "proxy" ldap server using 389 or openLDAP this server will
either sync or proxy to the server you have. This server can be
controlled by you and there you can map things the way you want using
native LDAP server capabilities or developing you own DS plugin that
would do what you need.
HTH
--
Thank you,
Dmitri Pal
Sr. Engineering Manager for IdM portfolio
Red Hat Inc.
-------------------------------
Looking to carve out IT costs?
www.redhat.com/carveoutcosts/