<div dir="ltr"><div><div>Hello Mikael,<br><br></div>I don't know if sssd.conf support this syntax, nor authconfig, but<br>that would not work for me anyway.<br><br></div><div>authconfig generates other configurations than sssd.conf such as<br>
pam_ldap.conf for example (which does not support dns discovery).<br></div><div><br></div><div> That's why I need to launch authconfig with explicit ldap servers<br></div><div>(and I don't want them to be declared in ldap_uri).<br>
<br>---<br></div><div>Olivier<br></div><div><br><br><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">2013/10/11 Michael Ströder <span dir="ltr"><<a href="mailto:michael@stroeder.com" target="_blank">michael@stroeder.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Fri, 11 Oct 2013 14:07:31 +0200 Olivier <<a href="mailto:ldap@guillard.nom.fr">ldap@guillard.nom.fr</a>> wrote<br>
<div class="im">> I have reported it as an authconfig bug, I think it might also be something<br>
> to be considered at sssd level : should'nt sssd use "dns_discovery_domain"<br>
> to look for ldap server rather than "ldap_uri" if borth parameters are<br>
> declared<br>
> in sssd.conf ?<br>
<br>
</div>Well, why not just use LDAP URI without hostport portion for initiating a<br>
DNS-based server lookup:<br>
<br>
ldapuri ldap:///dc=example,dc=com<br>
<br>
Could even suppport LDAPS<br>
<br>
ldapuri ldaps:///dc=example,dc=com<br>
<br>
Ciao, Michael.<br>
<br>
<br>
</blockquote></div><br></div>