Active Directory Integration with SSSD
I'm trying to set up Windows active directory integration with SSSD and realmd on a Red had 7 machine at my workplace. The goal is to let users log onto linux machines with their windows accounts.
I'm running into an issue that I'm having a hard time finding help with, when I try to login to the linux machine an error gets written to the log; [sdap_idmap_sid_to_unix] (0x0080): Could not convert objectSID [S-1-5-21-2303841414-160008165-815047518-2195312] to a UNIX ID I've read that it's probably because the SID number is too large. I've tried messing with the ldap_id_range_max/min values, but I end up running into an error when SSSD tries to start that the value is "out of range" when I make them too big (over 3000000000 or so) Does anyone have any experience with this and can help? |
The idmap range parameters control which range of Unix UIDs/GIDs are to be associated with Windows SIDs. Since a UID/GID is an unsigned 32 bit integer, you'll get an error message if you specify a number larger than 4,294,967,295.
The "could not convert objectSID" error message simply means that ID mapping isn't working. The length of the SID is of no consequence. I have no experience with SSSD, but it is my understanding that it takes over the id mapping tasks normally performed by Samba/winbindd, and that it supports algorithmic ID mapping (similar to the RID backend) and RFC 2307. Which setting are you using? And if you're using RFC 2307, is the AD UID field populated for the user account in question? |
I'm using realmd to join the domain. I had tried changing a bunch of the settings, but I narrowed it down to the idmapping causing the problem.
My sssd.config looks like this (DOMAIN is the domain I'm trying to authenticate in); Code:
[sssd] These are mostly defaults, except for the idmap_range values, I've been experimenting with all sorts of values and can't get anything to work. |
Anyone?
|
All times are GMT -5. The time now is 07:29 PM. |