Am Sun, 29 Mar 2020 19:56:18 +0200
schrieb Tobias Crefeld
The "manual" setup that I'm using is based on sssd. I prefer this approach because it's offering a kind of credential caching. This is providing some independence of the AD domain controllers which might be unavailable temporarily.
Just to complete this issue: I found a pretty good commented description for an AD integration using sssd at https://mwbrown.org/2018/05/10/ad-for-debian-with-saltstack/ . The post is about integrating a Debian system, not a SLES machine but with the helpful blog post at https://www.suse.com/c/the-sssd-active-directory-and-sles-12-and-15/ it is possible to do the necessary adaptations for SLES. For Salt newbies with few Python experience like me a reference like https://docs.saltstack.com/en/latest/py-modindex.html is important to do the adaptations. Actually this approach is based on sls files that were created (per vi) below /srv/salt and /srv/pillar starting with top.sls files. So it's not using the Configuration management or the Salt formulas of Uyuni's WebUI. The execution process can get triggered via WebUI with Systems / System Groups / "Apply system states" and below "Schedule" you can monitor the results. -- Gruss, Tobias Crefeld. xmpp (no email): crefeld@xabber.de -- To unsubscribe, e-mail: uyuni-users+unsubscribe@opensuse.org To contact the owner, e-mail: uyuni-users+owner@opensuse.org