Repository navigation
389-DS as AD relay for user/password(kerberos). #7914
Unanswered
ThomasGehPunkt
asked this question in
Q&A
Replies: 1 comment
|
To hit a wider audience it might be better to send this to 389-users@lists.fedoraproject.org to get more input from the community. We used to offer passSync/WinSync but this is now deprecated and is no longer supported. Now we suggest looking at FreeIPA and trusts. But for passSync/Winsync you can see information here, but like I said this is no longer supported or maintained: https://docs.redhat.com/en/documentation/red_hat_directory_server/11/html/administration_guide/windows_sync |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hello Developer Team,
im apologize if the thread is in the wrong branche and for my, maybe, complicated description.
I'd like to know if this scenario is possible to solve with 389-ds and how. We have an internal network where we want to use the AD User and Credential of die Active Directory Domain in the outer Network. Therefore we already have the RHEL like AlmaLinux Server connect to the AD with an computer account in the Domain via sssd. from the internal network only see the 389-ds Server and the clients should only connect to the 389-ds via sssd to get the user accounts from a copied OU of the AD where we have read right. The "computer account" should only be on the Ldap of the 398-ds server but the credentials should be ask by the edge-server (and also cached if possible). No bidirektional write should be done to the AD Ldap.
Is this solution possible to use 389-ds as a solution. If yes is there any reliable howto i can implement it in our internal network.
sincerely.. Thomas
All reactions