I am trying to join my mageia laptop to my Windows Active Directory and if possible to Azure AD.\
Checking on this webpage; https://docs.microsoft.com/en-us/azure/active-directory-domain-services/join-rhel-linux-vm
The problem is that the required packages cannot be found on Mageia.... like realmd it's only available on MGA5.
Packages like realmd sssd oddjob oddjob-mkhomedir are not available.
Are they included in other packages?.
I need to use "realm join --verbose AADDSCONTOSO.COM -U 'contosoadmin@AADDSCONTOSO.COM'" to join..
$ urpmq -y sssd
I have no experience with active directory. From it's description, sssd-ad may be what is needed.
All online tutorials I saw today refers to a "realmd" binaries.
On some RHEL8 / CentOS8 tutos, an install command:
# dnf install realmd sssd oddjob oddjob-mkhomedir adcli samba-common samba-common-tools krb5-workstation authselect-compat
Some above packages are no equivalent on Mageia.
Assigning this as RPM package request.
Assigning this package request to all packagers collectively. On a voluntary basis, one of them might, if there are no license or other legal issues, want to integrate it to the distribution and maintain it for bug and security fixes.
You might also want to join the packager team to maintain this piece of software: see https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
How to join mageia to Active Directory =>
Add realmd and adcli tools from RHEL8/CentOS8 to join Active Directory Domains, NEW PACKAGE REQUESTComponent:
RPM Packages =>
New RPM package request
We do have sssd. adcli is pretty handy and would be nice to have. The current sssd version actually expects that you have it, and uses it to rotate the machine account password periodically. The net command (from Samba) for joining doesn't work reliably with newer Windows versions.
The oddjob stuff isn't needed, as we have pam_mkhomedir in the pam package, and that can be used.
The realmd package isn't as useful as documentation makes it sound. It does multiple things incompletely and incorrectly by default, so you end up having to fix the configuration manually anyway, it doesn't save much effort over just reading documentation and doing the configuration manually. I wouldn't be in favor of bringing this package back, at least without fixing those things.
A better idea would be integrating Active Directory support into drakauth.