URL: https://github.com/SSSD/sssd/pull/100
Title: #100: Updation of sssd-ad man page for case when dyndns_refresh_interval
< 60 seconds
amitkumar50 commented:
"""
Hi,
Thanks for valuable comment.
I am planning to use this:
Note that lowest possible value is 60 seconds in-case if value is
URL: https://github.com/SSSD/sssd/pull/100
Title: #100: Updation of sssd-ad man page for case when dyndns_refresh_interval
< 60 seconds
lslebodn commented:
"""
On (04/12/16 04:07), amitkumar50 wrote:
>Kindly review this Pull request..
>
It would be good if you could keep all changes in one
URL: https://github.com/SSSD/sssd/pull/98
Title: #98: Changes done in man for case when dyndns_refresh_interval is
specified < 60 seconds
Label: +Rejected
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email
URL: https://github.com/SSSD/sssd/pull/98
Author: amitkumar50
Title: #98: Changes done in man for case when dyndns_refresh_interval is
specified < 60 seconds
Action: closed
To pull the PR as Git branch:
git remote add ghsssd https://github.com/SSSD/sssd
git fetch ghsssd pull/98/head:pr98
git
URL: https://github.com/SSSD/sssd/pull/98
Title: #98: Changes done in man for case when dyndns_refresh_interval is
specified < 60 seconds
lslebodn commented:
"""
Closing because there is a new pull request #100 for the same change.
"""
See the full comment at
URL: https://github.com/SSSD/sssd/pull/98
Title: #98: Changes done in man for case when dyndns_refresh_interval is
specified < 60 seconds
Label: -Changes requested
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send
On 25.11.2016 15:55, Sumit Bose wrote:
On Fri, Nov 25, 2016 at 02:19:10PM +0100, Jan Cholasta wrote:
Bump, Sumit, have you seen my comments? I haven't heard back from you.
Yes, I've seen it and added a comment about it on the page
URL: https://github.com/SSSD/sssd/pull/100
Title: #100: Updation of sssd-ad man page for case when dyndns_refresh_interval
< 60 seconds
pbrezina commented:
"""
Hi, thank you for your contribution. I would personally use different phrasing:
"Note that the lowest values possible is 60 seconds."
URL: https://github.com/SSSD/sssd/pull/100
Title: #100: Updation of sssd-ad man page for case when dyndns_refresh_interval
< 60 seconds
pbrezina commented:
"""
ok to test
"""
See the full comment at
https://github.com/SSSD/sssd/pull/100#issuecomment-264793956
URL: https://github.com/SSSD/sssd/pull/103
Author: pbrezina
Title: #103: sudo: do not store usn if no rules are found
Action: opened
PR body:
"""
When ldap doesn't contain any sudorule during the initial full refresh,
usn is set to 1 instead of remaining unset and we are trying to
search
On (05/12/16 14:44), supertwist...@gmail.com wrote:
>I'm trying to connect my server to a LDAP server. I get a correct answer after
>using *id* and *ldapsearch* commands. However, i still not able to login with
>SSH.
>
It would be good to move discussion to sssd-users mailing list.
>(Mon Dec
I'm trying to connect my server to a LDAP server. I get a correct answer after
using *id* and *ldapsearch* commands. However, i still not able to login with
SSH.
I can see on sssd_LDAP.log file that the server has received the request to
login with the user (myuser), but the request was
URL: https://github.com/SSSD/sssd/pull/103
Title: #103: sudo: do not store usn if no rules are found
lslebodn commented:
"""
There is a simple domain config with case_preserving
```
[domain/LDAP]
id_provider = ldap
ldap_uri = ldap://$SERVER
ldap_search_base =
URL: https://github.com/SSSD/sssd/pull/103
Title: #103: sudo: do not store usn if no rules are found
lslebodn commented:
"""
There is a simple domain config with case_preserving
```
[domain/LDAP]
id_provider = ldap
ldap_uri = ldap://$SERVER
ldap_search_base =
URL: https://github.com/SSSD/sssd/pull/89
Title: #89: nss: rewrite nss responder so it uses cache_req
lslebodn commented:
"""
There is a simple domain config with case_preserving
```
[domain/LDAP]
id_provider = ldap
ldap_uri = ldap://$SERVER
ldap_search_base =
BTW, is there an option to edit messages here?
___
sssd-devel mailing list -- sssd-devel@lists.fedorahosted.org
To unsubscribe send an email to sssd-devel-le...@lists.fedorahosted.org
URL: https://github.com/SSSD/sssd/pull/89
Title: #89: nss: rewrite nss responder so it uses cache_req
lslebodn commented:
"""
SSS_SEED user offline authentication failed:
* block access to the ldap
* sleep a bit (e.g. 4 seconds)
* seed the SSSD cache with a user: sss_seed -D LDAP -n seeduser -u
> On (05/12/16 14:44), supertwisters(a)gmail.com wrote:
> It would be good to move discussion to sssd-users mailing list.
>
> I think the log is crystal clear.
> "Authentication failure". It might be a wrong password; or denial due to
> password policy or something else. It's hard to say without
URL: https://github.com/SSSD/sssd/pull/103
Title: #103: sudo: do not store usn if no rules are found
lslebodn commented:
"""
Jakub reviewed https://fedorahosted.org/sssd/ticket/2970 and overlooked such
small issue. :-)
we should let him to review it one more time
"""
See the full comment at
URL: https://github.com/SSSD/sssd/pull/89
Title: #89: nss: rewrite nss responder so it uses cache_req
lslebodn commented:
"""
There is also a crash for group enumeration
```
(Wed Nov 30 09:22:36 2016) [sssd[nss]] [cache_req_search_done] (0x0400): CR #0:
Returning updated object [Groups
URL: https://github.com/SSSD/sssd/pull/89
Title: #89: nss: rewrite nss responder so it uses cache_req
lslebodn commented:
"""
Regression test for https://fedorahosted.org/sssd/ticket/2865 failed
or it was https://fedorahosted.org/sssd/ticket/2170
Following C-code was executed for existing and
21 matches
Mail list logo
