[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-13 Thread jhrozek
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts jhrozek commented: """ * master: 39d6a3be119b050b0690152b6b443117c8617b1c """ See the full comment at https://github.com/SSSD/sssd/pull/432#issuecomment-343970599 ___

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-13 Thread fidencio
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts fidencio commented: """ @justin-stephenson, nice, thanks! I'm adding the "Accepted" label to this PR based on the discussion we had during the team meeting and in the feedback provided by @j

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-13 Thread justin-stephenson
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts justin-stephenson commented: """ @fidencio man page verbiage looks good to me. """ See the full comment at https://github.com/SSSD/sssd/pull/432#issuecomment-343960502 __

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-10 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ Here is the issue that tracks the email in 'nameAlias' attribute issue: https://pagure.io/SSSD/sssd/issue/3567 """ See the full comment at https://github.com/SSSD/s

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-10 Thread fidencio
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts fidencio commented: """ Just for the record. We had a meeting Yesterday and we discussed this PR face-to-face in order to speed the process up and do not block it. @lslebodn's worries **do**

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ On 11/03/2017 05:41 PM, lslebodn wrote: > On (03/11/17 16:19), mzidek-rh wrote: > >No, I used good example. Your example is the wrong one and would not > trigger the

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ On (03/11/17 16:36), mzidek-rh wrote: >Sorry, but this: >``` >(Fri Nov 3 15:52:42 2017) [sssd[nss]] [sysdb_getpwnam] (0x0020): Search for >[ema...@ipadomain.test] ret

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ On (03/11/17 16:19), mzidek-rh wrote: >No, I used good example. Your example is the wrong one and would not trigger >the error. > There are more ways how you can sto

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ Sorry, but this: ``` (Fri Nov 3 15:52:42 2017) [sssd[nss]] [sysdb_getpwnam] (0x0020): Search for [ema...@ipadomain.test] returned multiple results. It can be an emai

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ On (03/11/17 15:21), mzidek-rh wrote: >About logging message to syslog. I am not against it. I wanted to solve it by >MAN + DEBUG. MAN + DEBUG + SYSLOG, looked like o

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ No, I used good example. Your example is the wrong one and would not trigger the error. What do you think will happen if in my example scenario I search for 'getent

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ On (03/11/17 15:06), mzidek-rh wrote: >It will not generate the message you wrote. >It will never show shortname in the output. Yes, I forgot to use fqname there. But

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ About logging message to syslog. I am not against it. I wanted to solve it by MAN + DEBUG. MAN + DEBUG + SYSLOG, looked like overkill to me, especially given that w

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ You are wrong. It will not generate the message you wrote. It will never show shortname in the output. It will not generate the error if you search by username that is

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ On (03/11/17 14:26), mzidek-rh wrote: >mzidek-rh commented on this pull request. >> @@ -218,6 +218,21 @@ int sysdb_getpwnam(TALLOC_CTX *mem_ctx, > goto done; >

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ I added a note to the commit message. """ See the full comment at https://github.com/SSSD/sssd/pull/432#issuecomment-341719462 __

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ BTW all non-clear parts which were explained in PR should have been part of commit message. """ See the full comment at https://github.com/SSSD/sssd/pull/432#issuec

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ By namealias I meant SYSDB_NAME_ALIAS if it was not clear. """ See the full comment at https://github.com/SSSD/sssd/pull/432#issuecomment-341698043 _

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ The problem is with multiple users sharing the same email in LDAP/IPA. The email attribute from LDAP is stored twice in the local SYSDB database. Once as the SYSDB_U

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ >You are wrong. As I wrote in one of the previous comments: >"Just a note, we do not use SYSDB_USER_EMAIL in getpwnam searches. We >lowercase the attribute >and store

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ >You are wrong. As I wrote in one of the previous comments: >"Just a note, we do not use SYSDB_USER_EMAIL in getpwnam searches. We >lowercase the attribute >and store

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread mzidek-rh
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts mzidek-rh commented: """ You are wrong. As I wrote in one of the previous comments: "Just a note, we do not use SYSDB_USER_EMAIL in getpwnam searches. We lowercase the attribute and store it

[SSSD] [sssd PR#432][comment] CACHE_REQ: Better debugging for email conflicts

2017-11-03 Thread lslebodn
URL: https://github.com/SSSD/sssd/pull/432 Title: #432: CACHE_REQ: Better debugging for email conflicts lslebodn commented: """ I'm sorry the error message is still vague and it will not fix the bug. NACK. `SYSDB_USER_EMAIL` is part of attributes requested in `SYSDB_PW_ATTRS` and used in many