FreeRadius Integration with Microsoft Active Directory
Hi Marco, Thank you for your response. From your response I understand, even if my AD Domain is running on MS (Microsoft), I can join the RHEL to AD domain using 'winbind daemon', which I did. After joining the RHEL 8 Server to domain, 'winbind' is still not working, it's giving the below error. [root@localhost.domain.com]# wbinfo -a FreeRADIUSdev2 Enter FreeRADIUSdev2's password: plaintext password authentication failed Could not authenticate user FreeRADIUSdev2 with plaintext password Enter FreeRADIUSdev2's password: could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE could not obtain winbind separator! could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE could not obtain winbind netbios name! could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE could not obtain winbind domain name! Failed to get domain from winbindd Could not authenticate user FreeRADIUSdev2 with challenge/response Regards Raman Singh When replying, please edit your Subject line so it is more specific than "Re: Contents of Freeradius-Users digest..." Today's Topics: 1. Re: FreeRadius Integration with Microsoft Active Directory (Marco Gaiarin) ---------------------------------------------------------------------- Message: 1 Date: Sun, 8 Jan 2023 18:09:08 +0100 From: Marco Gaiarin <gaio@lilliput.linux.it> To: "Singh, Ramanpreet via Freeradius-Users" <freeradius-users@lists.freeradius.org> Cc: freeradius-users@lists.freeradius.org Subject: Re: FreeRadius Integration with Microsoft Active Directory Message-ID: <iu9r8j-qi55.ln1@hermione.lilliput.linux.it> Mandi! Singh, Ramanpreet via Freeradius-Users In chel di` si favelave...
I read above links where it has been mentioned to used samba for AD integration, however this requires SAMBA AD-DC, which we don't have in our enviornment.
No, you need an AD domain (samba or MS, it is the same) and a linux box with a winbind daemon running: both the domain member and domain controller configuration work, but it suffices you install winbind, configure samba (smb.conf) as domain member and join the domain. -- There are only 10 kinds of people in the world -- Those who understand binary, and those who don't. (Roberto Maglica) ------------------------------ Subject: Digest Footer - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html ------------------------------ End of Freeradius-Users Digest, Vol 213, Issue 5 ************************************************ ------------------------------------------------------------------------------ External Email: Please use caution when opening links and attachments / Courriel externe: Soyez prudent avec les liens et documents joints
On Jan 9, 2023, at 12:17 PM, Singh, Ramanpreet via Freeradius-Users <freeradius-users@lists.freeradius.org> wrote:
Thank you for your response. From your response I understand, even if my AD Domain is running on MS (Microsoft), I can join the RHEL to AD domain using 'winbind daemon', which I did.
As I said.... the documentation is correct. Marco is correct that winbind is needed, but you *also* need Samba. FreeRADIUS talks to Winbind. Winbind connects to Samba. Samba joins the AD domain. This is all documented. Follow the documentation and it will work.
After joining the RHEL 8 Server to domain, 'winbind' is still not working, it's giving the below error.
[root@localhost.domain.com]# wbinfo -a FreeRADIUSdev2 Enter FreeRADIUSdev2's password: plaintext password authentication failed Could not authenticate user FreeRADIUSdev2 with plaintext password Enter FreeRADIUSdev2's password: could not obtain winbind interface details: WBC_ERR_WINBIND_NOT_AVAILABLE could not obtain winbind separator!
This is an issue with winbind and/or Samba. Ask the Samba people how their software works. Alan DEKok.
participants (2)
-
Alan DeKok -
Singh, Ramanpreet