Dear sssd team,
I have deployed several Workstations (in Fedora or Centos) configured with sssd vs Ad according to the wiki documentation page : https://fedorahosted.org/sssd/wiki/Configuring_sssd_with_ad_server
It is working great, and I am satisfied with this solution. On my network, home users are centralized on a netapp filer compatible with NIS and kerberos services furnished by the Windows 2012 R2 AD controlers (called mixed mode at netapp). So when a linux user login, he is directly using his homedir through NFS and NIS service. For Windows user, he can logon on a windows station and retrieves his home space mounted on a windows drives.
I was looking on the future Windows Server 2016 and starting to worry because Identity Management for Unix (IDMU) & NIS Server Role will not be parts the 2016 version. I found this article https://blogs.technet.microsoft.com/activedirectoryua/2016/02/09/identity-management-for-unix-idmu-is-deprecated-in-windows-server/
Does someone from the sssd team hears about this ? What will be planned for 2016 windows server wersion on SSSD side ? Should I already think to others alternatives ? Which ones do you advice : FreeIPA / LDAP / ?
The main problem will be to reconfigure the netapp filer, it is so easy to configure with actual AD Windows server with NIS services... I don't know to do it with LDAP / FreeIpa
Best Regards
as far as I understand that only the management UI is going away, as the second half of the https://blogs.technet.microsoft.com/activedirectoryua/2016/02/09/identity-management-for-unix-idmu-is-deprecated-in-windows-server/ it is still possible to configure the attributes.
btw SSSD also supports ID mapping and FreeIPA supports setting 'overrides' for individual users or groups.
Hello, Thanks for your answer. you are right, Unix Attributes seems to be conserved.
It is wrtten : "For example, you may require the RFC 2307 attributes in combination with Network File System (NFS) Server (which does not require NIS Server role to be installed on Windows Server) to map the identity."
In my case, I am usind sssd with homedir located on a NFS export. I think my netapp filer is using NIS service to match UID / GUID acess. I do not know how it will work without a NIS service on the AD controler... Obviously, this is not related to sssd.
But would it be usefull to get a new Wiki page for sssd vs AD 2016 due to all these changes ?
May you indicate me what is the meaning of ID mapping and setting 'overrides' for individual users or groups in freeipa ?
Do you have an idea of what you want to see on such wiki page? If yes, you are definitely welcome to create one.
About FreeIPA:
We already have https://fedorahosted.org/sssd/wiki/Configuring_sssd_with_ad_server I think adding a paragraph would work there.
edg91, I was wondering if you could help us craft this paragraph? From my point of view, just adding a note and linking to the technet blog would be sufficient, do you agree?
Fields changed
type: defect => task
Hello,
It would be nice to add the link to the technet blog, as windows server 2016 is not yet available (except preview). Did someone test sssd vs AD 2016 (preview) ?
Is it worth adding informations about alternatives to AD ? like freeipa, or others ? It would help people make a decision concerning the best way to choose.
I'm not sure anyone tested 2016 (I certainly didn't).
I agree it would be nice to mention IPA's ID views at least.
OK, I did a basic smoke-test win Server 2016 preview and the basic tasks (logins including GPO access control) work fine.
I also amended the AD setup howto we have on the wiki: https://fedorahosted.org/sssd/wiki/Configuring_sssd_with_ad_server?action=diff&version=18&old_version=17
Please review :)
by the way, the only issue I saw with 2016 was that SSSD didn't recognize its Domain Controller value from rootDSE, so it reverted to win-2003 compatibility mode. I sent a patch upstream to fix that.
Wiki update is ok for me. Thank you
Thanks for checking. I'm closing the ticket.
resolution: => fixed status: new => closed
rhbz: => 0
Metadata Update from @edg91: - Issue set to the milestone: NEEDS_TRIAGE
SSSD is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in SSSD's github repository.
This issue has been cloned to Github and is available here: - https://github.com/SSSD/sssd/issues/4022
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.