[SSSD-users] Re: problems with sssd-1.9
I used the files located here:
https://copr-be.cloud.fedoraproject.org/results/sgallagh/sssd-1.9-rhel5/epel-5-x86_64/
Yes, libsss_ad.so is in the package. I used samba3x-3.6.23.
Andrea
-Original Message-
From: Jakub Hrozek [mailto:jhro...@redhat.com]
Sent: Thursday, July 19, 2018 4:04 AM
To: End-user discussions about the System Security Services Daemon
Subject: {EXTERNAL} [SSSD-users] Re: problems with sssd-1.9
> On 18 Jul 2018, at 21:13, Laack, Andrea P 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@lists.fedorahosted.org To unsubscribe
send an email to sssd-users-le...@lists.fedorahosted.org
Fedora Code of Conduct:
https://urldefense.proofpoint.com/v2/url?u=https-3A__getfedora.org_code-2Dof-2Dconduct.html=DwIGaQ=qhent5lL-8Lans1hhN7NTGhSd0GBLfQfwUvzHj1D5tQ=U7-RwMM5aSl714ZiiWB9Ly-4UTAgbRqq8xuylndqN_8=kKX8OC4f8tsbUFDRZW5NTMWwPDXhi1pbl_vxtxuX0I8=UZjn24_mWi0zpXZtIwkPo3L_UffZncib2Svhf8zVMfs=
List Guidelines:
https://urldefense.proofpoint.com/v2/url?u=https-3A__fedoraproject.org_wiki_Mailing-5Flist-5Fguidelines=DwIGaQ=qhent5lL-8Lans1hhN7NTGhSd0GBLfQfwUvzHj1D5tQ=U7-RwMM5aSl714ZiiWB9Ly-4UTAgbRqq8xuylndqN_8=kKX8OC4f8tsbUFDRZW5NTMWwPDXhi1pbl_vxtxuX0I8=8trw0nwPOUk21hsE0TtaDSbQp3VXeKEPs988RDVpa1w=
List Archives:
https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.fedoraproject.org_archives_list_sssd-2Dusers-40lists.fedorahosted.org_message_HOYRVOP42MLPSXEM2OM46LRKYVFY7DGP_=DwIGaQ=qhent5lL-8Lans1hhN7NTGhSd0GBLfQfwUvzHj1D5tQ=U7-RwMM5aSl714ZiiWB9Ly-4UTAgbRqq8xuylndqN_8=kKX8OC4f8tsbUFDRZW5NTMWwPDXhi1pbl_vxtxuX0I8=d058Yc__ULNnqz8Y-_ilMfPwPmGpDH8LBAa-qSRMqBc=
**
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.
___
sssd-users mailing list -- sssd-users@lists.fedorahosted.org
To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/sssd-users@lists.fedorahosted.org/message/ZTWXW7K2PO3PP7PJVOLYGG5MQ3TDV3UY/
[SSSD-users] Re: problems with sssd-1.9
> On 18 Jul 2018, at 21:13, Laack, Andrea P 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@lists.fedorahosted.org To unsubscribe send an email to sssd-users-le...@lists.fedorahosted.org Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/sssd-users@lists.fedorahosted.org/message/HOYRVOP42MLPSXEM2OM46LRKYVFY7DGP/
[SSSD-users] Re: problems with sssd-1.9
[domain\xxx.pvt] Is the backslash valid here? I am sure an expert will say yes.. You are well aware that RHEL 5 is out of support lifetime? I would imagine that you have some critical applications which run on these machines though. From: Laack, Andrea P Sent: 18 July 2018 21:13:47 To: sssd-users@lists.fedorahosted.org Subject: [SSSD-users] problems with sssd-1.9 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. Here is what I got: [root@testcentos5 db]# /usr/sbin/sssd -i -d9 (Wed Jul 18 13:18:49:136142 2018) [sssd] [ldb] (0x0400): server_sort:Unable to register control with rootdse! (Wed Jul 18 13:18:49:137532 2018) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 0) (Wed Jul 18 13:18:49:137857 2018) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:137962 2018) [sssd] [ldb] (0x4000): commit ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138029 2018) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138161 2018) [sssd] [ldb] (0x4000): commit ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138226 2018) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138343 2018) [sssd] [ldb] (0x4000): commit ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138404 2018) [sssd] [ldb] (0x4000): start ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138502 2018) [sssd] [ldb] (0x4000): commit ldb transaction (nesting: 1) (Wed Jul 18 13:18:49:138660 2018) [sssd] [confdb_create_ldif] (0x0400): Processing config section [sssd] (Wed Jul 18 13:18:49:138784 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [config_file_version] (Wed Jul 18 13:18:49:138870 2018) [sssd] [confdb_create_ldif] (0x4000): config_file_version: 2 (Wed Jul 18 13:18:49:138945 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [domains] (Wed Jul 18 13:18:49:139034 2018) [sssd] [confdb_create_ldif] (0x4000): domains: xxx.pvt (Wed Jul 18 13:18:49:139130 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [services] (Wed Jul 18 13:18:49:139214 2018) [sssd] [confdb_create_ldif] (0x4000): services: nss, pam (Wed Jul 18 13:18:49:139295 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [debug_level] (Wed Jul 18 13:18:49:139374 2018) [sssd] [confdb_create_ldif] (0x4000): debug_level: 9 (Wed Jul 18 13:18:49:139539 2018) [sssd] [confdb_create_ldif] (0x4000): Section dn dn: cn=sssd,cn=config cn: sssd config_file_version: 2 domains: xxx.pvt services: nss, pam debug_level: 9 (Wed Jul 18 13:18:49:139873 2018) [sssd] [confdb_create_ldif] (0x0400): Processing config section [nss] (Wed Jul 18 13:18:49:139972 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [debug_level] (Wed Jul 18 13:18:49:140046 2018) [sssd] [confdb_create_ldif] (0x4000): debug_level: 9 (Wed Jul 18 13:18:49:140113 2018) [sssd] [confdb_create_ldif] (0x4000): Section dn dn: cn=nss,cn=config cn: nss debug_level: 9 (Wed Jul 18 13:18:49:140193 2018) [sssd] [confdb_create_ldif] (0x0400): Processing config section [domain\xxx.pvt] (Wed Jul 18 13:18:49:140280 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [fallback_homedir] (Wed Jul 18 13:18:49:140372 2018) [sssd] [confdb_create_ldif] (0x4000): fallback_homedir: /home/%u (Wed Jul 18 13:18:49:140372 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [default_shell] (Wed Jul 18 13:18:49:140372 2018) [sssd] [confdb_create_ldif] (0x4000): default_shell: /bin/bash (Wed Jul 18 13:18:49:140372 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [ad_domain] (Wed Jul 18 13:18:49:140377 2018) [sssd] [confdb_create_ldif] (0x4000): ad_domain: xxx.pvt (Wed Jul 18 13:18:49:140453 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [krb5_realm] (Wed Jul 18 13:18:49:140536 2018) [sssd] [confdb_create_ldif] (0x4000): krb5_realm: xxx.PVT (Wed Jul 18 13:18:49:140613 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [krb5_server] (Wed Jul 18 13:18:49:140690 2018) [sssd] [confdb_create_ldif] (0x4000): krb5_server: c02.xxx.pvt (Wed Jul 18 13:18:49:140765 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [auth_provider] (Wed Jul 18 13:18:49:140842 2018) [sssd] [confdb_create_ldif] (0x4000): auth_provider: krb5 (Wed Jul 18 13:18:49:141316 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [cache_credentials] (Wed Jul 18 13:18:49:141640 2018) [sssd] [confdb_create_ldif] (0x4000): cache_credentials: True (Wed Jul 18 13:18:49:141839 2018) [sssd] [confdb_create_ldif] (0x0400): Processing attribute [id_provider] (Wed Jul 18 13:18:49:141945 2018) [sssd] [confdb_create_ldif] (0x4000): id_provider: ad (Wed Jul 18 13:18:49:142023 2018) [sssd] [confdb_create_ldif] (0x0400):
