Are you sure that swapping just the sssd version makes your setup works
with identical autofs configuration and sssd.conf? When looking for
'what broke my setup', it's best to only change one component at a time.
I don't think we did many changes to autofs between 1.9 and 1.11, so I'm
a bit surprised something is not working.
Can you see the maps you expect when you run automounter -m ?
Can you paste the complete logs (domain and autofs) after you restart
automounter, which should re-read all maps, including when you request
the map?

I know you figured out already, but for reference and anyone else
reading the thread -- even if id_provider=ad would select the right
authentication options, other provider set to ldap (like
autofs_provider=ldap, others had same problems with sudo) would select
the LDAP defaults again, which is anonymous binds.
We should implement autofs_provider=ad one of these days..

On Fri, May 23, 2014 at 12:10:14PM +0200, steve wrote:
> Would it be possible to include the PTR update as part of the ad backend?
> Cheers,
> Steve
According to man sssd-ad, dyndns_update_ptr should be set to True in the
AD backend. Do you not see the PTR records updated? Anything interesting
in the logs?

On 23/05/14 12:43, Jakub Hrozek wrote:
>On Fri, May 23, 2014 at 12:10:14PM +0200, steve wrote:
>>Would it be possible to include the PTR update as part of the ad backend?
>>Cheers,
>>Steve
>
>According to man sssd-ad, dyndns_update_ptr should be set to True in the
>AD backend. Do you not see the PTR records updated? Anything interesting
>in the logs?
We only get A and AAAA:
(Thu May 22 12:18:20 2014) [sssd[be[hh3.site]]]
[be_nsupdate_create_fwd_msg] (0x0400): -- Begin nsupdate message --
realm HH3.SITE
update delete lubuntu-laptop. in A
send
update delete lubuntu-laptop. in AAAA
send
update add lubuntu-laptop. 3600 in A 192.168.1.22
send

The PTR update is a separate one, I need to see more context from the
logs.
If the PTR update was off, you would see a DEBUG message from
"sdap_dyndns_update_done" saying "No PTR update requested, done\n"

On Fri, May 23, 2014 at 12:54:59PM +0200, steve wrote:
> On 23/05/14 12:43, Jakub Hrozek wrote:
>> On Fri, May 23, 2014 at 12:10:14PM +0200, steve wrote:
>>> Would it be possible to include the PTR update as part of the ad backend?
>>> Cheers,
>>> Steve
>>
>> According to man sssd-ad, dyndns_update_ptr should be set to True in the
>> AD backend. Do you not see the PTR records updated? Anything interesting
>> in the logs?
>
> We only get A and AAAA:
> (Thu May 22 12:18:20 2014) [sssd[be[hh3.site]]]
> [be_nsupdate_create_fwd_msg] (0x0400): -- Begin nsupdate message --
> realm HH3.SITE
> update delete lubuntu-laptop. in A
> send
> update delete lubuntu-laptop. in AAAA
> send
> update add lubuntu-laptop. 3600 in A 192.168.1.22
> send
The PTR update is a separate one, I need to see more context from the
logs.
If the PTR update was off, you would see a DEBUG message from
"sdap_dyndns_update_done" saying "No PTR update requested, done\n"