summaryrefslogtreecommitdiff
path: root/COPYING
diff options
context:
space:
mode:
authorSumit Bose <sbose@redhat.com>2012-11-09 21:31:23 +0100
committerJakub Hrozek <jhrozek@redhat.com>2012-11-14 10:42:34 +0100
commit5063dcc5ab685dce325b13b9c1e93cee2a673e60 (patch)
treea3bbb1ed9771246569250dca33557cb7d1b684b4 /COPYING
parent778491bebee536a196afc29b0d9953843a5374b2 (diff)
downloadsssd-5063dcc5ab685dce325b13b9c1e93cee2a673e60.tar.gz
sssd-5063dcc5ab685dce325b13b9c1e93cee2a673e60.tar.bz2
sssd-5063dcc5ab685dce325b13b9c1e93cee2a673e60.zip
Run IPA subdomain provider if IPA ID provider is configured
To make configuration easier the IPA subdomain provider should be always loaded if the IPA ID provider is configured and the subdomain provider is not explicitly disabled. But to avoid the overhead of regular subdomain requests in setups where no subdomains are used the IPA subdomain provider should behave differently if configured explicit or implicit. If the IPA subdomain provider is configured explicitly, i.e. 'subdomains_provider = ipa' can be found in the domain section of sssd.conf subdomain request are always send to the server if needed. If it is configured implicitly and a request to the server fails with an indication that the server currently does not support subdomains at all, e.g. is not configured to handle trust relationships, a new request will be only send to the server after a long timeout or after a going-online event. To be able to make this distinction this patch save the configuration status to the subdomain context. Fixes https://fedorahosted.org/sssd/ticket/1613
Diffstat (limited to 'COPYING')
0 files changed, 0 insertions, 0 deletions