I discussed the enhancement with the autofs maintainer and here is the proposal:

The automounter only reads the master map on startup or when it receives SIGHUP (which is an explicit way of telling the automounter to re-read its configuration). That means it's quite a rare event, at the same time modifications to the master map are quite rare. In both cases the admin expects the changes to the map to propagate to the automounter deamon.

In SSSD, we should implement the same behaviour the automounter implements internally, which is:
1. when a request comes for the master map, completely bypass caching and go to the Data Provider
2. the master map is called auto.master in 99% of the cases. For the 1% where it's not, we might want to implement an option to override the map name (automounter has that option).

design: =>
design_review: => 0
fedora_test_page: =>

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.9.3
type: enhancement => defect

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=870045

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=870045 870045]

Not critical for 1.9.3

_comment0: Not critical for 1.9.4 => 1352200480568757
milestone: SSSD 1.9.3 => SSSD 1.9.4

Linked to Bugzilla bug: https://bugzilla.redhat.com/show_bug.cgi?id=876531 (Red Hat Enterprise Linux 6)

rhbz: [https://bugzilla.redhat.com/show_bug.cgi?id=870045 870045] => [https://bugzilla.redhat.com/show_bug.cgi?id=870045 870045], [https://bugzilla.redhat.com/show_bug.cgi?id=876531 876531]

Fields changed

owner: somebody => jhrozek
patch: 0 => 1
status: new => assigned

• master:
  • ccb2c1f
  • e880949
  • 1bcb68c
  • 08c72b8
  • 06cb67c
  • ba15330
  • 6ab9f47
• sssd-1-9:
  • 10bfd01
  • c65afc2
  • 286b115
  • a0d1219
  • 05bc499
  • fb4cb94
  • 20798b1

resolution: => fixed
status: assigned => closed

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2634

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.