-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 10/10/2013 10:39 AM, Olivier wrote:
Here it comes again...
I have an issue with this deployment plan.
I use a script to deploy the client configuration. Outside of other
things, the script write a fresh sssd.conf (including
"dns_discovery_domain" and "ldap_backup_uri" as discussed), and
then launch authconfig.
The problem is the following :
since my "fresh" sssd.conf doesn't include any "ldap_uri" (I
don't
need any since I want to use the DNS service discovery), then
authconfig add this tuning.
When I look at the transactions with tshark, it sounds like sssd
is ignoring the "dns_discovery_domain" (and use ldap servers as
declared in "ldap_uri").
Do you confirm ?
Question : is there any way to avoid authconfig configuring
"ldap_uri" in sssd.conf if "dns_discovery_domain" is already tuned
?
Other comment ?
This sounds like a pretty clear bug in authconfig. Would you mind
filing it at
https://bugzilla.redhat.com/enter_bug.cgi?product=Fedora&component=au...
please?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.14 (GNU/Linux)
Comment: Using GnuPG with Thunderbird -
http://www.enigmail.net/
iEYEARECAAYFAlJW9OQACgkQeiVVYja6o6PlRgCfbbL5kS5i/6MD1qanH13Mq4Mw
ZeAAn1yDCxlj+VGxbLzVx8vhr8E04zKc
=AGMd
-----END PGP SIGNATURE-----