6:47 a.m.
I used the files located here:
https://copr-be.cloud.fedoraproject.org/results/sgallagh/sssd-1.9-rhel5/e...
Yes, libsss_ad.so is in the package. I used samba3x-3.6.23.
Andrea
-----Original Message-----
From: Jakub Hrozek [mailto:jhrozek@redhat.com]
Sent: Thursday, July 19, 2018 4:04 AM
To: End-user discussions about the System Security Services Daemon
<sssd-users(a)lists.fedorahosted.org>
Subject: {EXTERNAL} [SSSD-users] Re: problems with sssd-1.9
On 18 Jul 2018, at 21:13, Laack, Andrea P
<Andrea.Laack(a)BSWHealth.org> wrote:
I have been tasked with joining a number of redhat/centos 5 servers to a domain. I found
sssd-1.9 that would allow id_provider ad. This is Centos 5.11.
Well, the upstream 1.9 had the ad_provider bits, but they are not built by default IIRC,
because the samba libraries on RHEL-5 were too old. You can check by running rpm -ql sssd
and checking if there is libsss_ad.so..
_______________________________________________
sssd-users mailing list -- sssd-users(a)lists.fedorahosted.org To unsubscribe send an email
to sssd-users-leave(a)lists.fedorahosted.org
Fedora Code of Conduct:
https://urldefense.proofpoint.com/v2/url?u=https-3A__getfedora.org_code-2...
List Guidelines:
https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wi...
List Archives:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject....
**********************************************************************
The information contained in this e-mail may be privileged and/or confidential, and
protected from disclosure, and no waiver of any attorney-client, work product, or other
privilege is intended. If you are the intended recipient, further disclosures are
prohibited without proper authorization. If you are not the intended recipient (or have
received this e-mail in error) please notify the sender immediately and destroy this
e-mail. Any unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden and possibly a violation of federal or state law and
regulations. The sender and Baylor Scott & White Health, and its affiliated entities,
hereby expressly reserve all privileges and confidentiality that might otherwise be waived
as a result of an erroneous or misdirected e-mail transmission. No employee or agent is
authorized to conclude any binding agreement on behalf of Baylor Scott & White Health,
or any affiliated entity, by e-mail without express written confirmation by the CEO, the
Senior Vice President of Supply Chain Services or other duly authorized representative of
Baylor Scott & White Health.