sssd.git/src/man, branch simo Unnamed repository; edit this file to name it for gitweb. try primary server after retry_timeout + 1 seconds when switching to backup 2012-12-18T15:40:51+00:00 Pavel Březina pbrezina@redhat.com 2012-12-17T11:04:54+00:00 e148ba6dbb26a0eac162ac9a2ff550da2c883808 https://fedorahosted.org/sssd/ticket/1679 The problem is when we are about to reset the server status, we don't get through the timeout (30 seconds) because the "switch to primary server" task is scheduled 30 seconds after fall back to a backup server. Thus the server status remains "not working" and is resetted after another 30 seconds. We need to make sure that the server status is tried after the timeout period. retry_timeout is currently hardcoded to 30, thus the change in man page. 
https://fedorahosted.org/sssd/ticket/1679

The problem is when we are about to reset the server status, we don't
get through the timeout (30 seconds) because the "switch to primary
server" task is scheduled 30 seconds after fall back to a backup
server. Thus the server status remains "not working" and is resetted
after another 30 seconds.

We need to make sure that the server status is tried after the
timeout period. retry_timeout is currently hardcoded to 30, thus
the change in man page.
MAN: Fix the title of sssd-sudo 2012-12-13T20:01:24+00:00 Jakub Hrozek jhrozek@redhat.com 2012-12-11T17:12:43+00:00 04b0ea7402f3268d382143493f5f12aa0bfe1a2b https://fedorahosted.org/sssd/ticket/1710 
https://fedorahosted.org/sssd/ticket/1710
sudo manpage: clarify that sudoHost may contain wildcards and not regular expression 2012-12-11T13:38:57+00:00 Pavel Březina pbrezina@redhat.com 2012-12-09T16:30:39+00:00 b24712874c686977465a551a3129133cec884584 https://fedorahosted.org/sssd/ticket/1690 
https://fedorahosted.org/sssd/ticket/1690
MAN: Move ssh_known_hosts_timeout documentation to the correct section 2012-12-05T22:55:12+00:00 Jan Cholasta jcholast@redhat.com 2012-12-05T09:58:55+00:00 90f4d0cec9245d8f6838044408a38d6d31101777 






LDAP: Make it possible to use full principal in ldap_sasl_authid again
2012-11-19T21:19:29+00:00

Jakub Hrozek
jhrozek@redhat.com

2012-11-19T16:34:56+00:00

24c3186d01d8d1c11832baab24ab3f0de121c666












MAN: document the ldap_sasl_realm option
2012-11-19T21:19:29+00:00

Jakub Hrozek
jhrozek@redhat.com

2012-11-19T09:32:53+00:00

73291a9e0b9bcaf56e9858c7ea2226b5b0f6e26c

The option was completely undocumented.





The option was completely undocumented.







MAN: quotation fix
2012-11-16T14:39:26+00:00

Ondrej Kos
okos@redhat.com

2012-11-16T14:27:07+00:00

f70dc1039451863bebb1a3af5d6eb027f40de8e7

I noticed that the proxy in auth_provider section of sssd.conf manpage
isn't quoted when all others are.





I noticed that the proxy in auth_provider section of sssd.conf manpage
isn't quoted when all others are.







Add ignore_group_members option.
2012-11-15T19:03:27+00:00

Paul B. Henson
henson@acm.org

2012-11-13T11:31:43+00:00

59f136cd254d1acf2991c97221eb08803784777d

https://fedorahosted.org/sssd/ticket/1376





https://fedorahosted.org/sssd/ticket/1376







Run IPA subdomain provider if IPA ID provider is configured
2012-11-14T09:42:34+00:00

Sumit Bose
sbose@redhat.com

2012-11-09T20:31:23+00:00

5063dcc5ab685dce325b13b9c1e93cee2a673e60

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





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







Always start PAC responder if IPA ID provider is configured
2012-11-14T09:42:34+00:00

Sumit Bose
sbose@redhat.com

2012-11-13T20:21:38+00:00

778491bebee536a196afc29b0d9953843a5374b2

Since the PAC responder is used during the authentication of users from
trusted realms it is started automatically if the IPA ID provider is
configured for a domain to simplify the configuration.

Fixes https://fedorahosted.org/sssd/ticket/1613





Since the PAC responder is used during the authentication of users from
trusted realms it is started automatically if the IPA ID provider is
configured for a domain to simplify the configuration.

Fixes https://fedorahosted.org/sssd/ticket/1613