[SSSD-users] Re: SSSD/AD Issues After 1.14 to 1.15 upgrade in CentOS 7

The preffered place is https://pagure.io/SSSD/sssd/new_issue On Fri, Feb 02, 2018 at 05:59:18PM +, Simon Engelbert wrote: > Sure, where is the proper place to file tickets? > > - Simon > On 2018-02-02, 10:20 AM, "Jakub Hrozek" wrote: > > If you can reproduce this

[SSSD-users] Re: SSSD/AD Issues After 1.14 to 1.15 upgrade in CentOS 7

Sure, where is the proper place to file tickets? - Simon On 2018-02-02, 10:20 AM, "Jakub Hrozek" wrote: If you can reproduce this with a recent build, please file a ticket.. On Fri, Feb 02, 2018 at 05:01:25PM +, Simon Engelbert wrote: > We updated to

[SSSD-users] Re: SSSD/AD Issues After 1.14 to 1.15 upgrade in CentOS 7

If you can reproduce this with a recent build, please file a ticket.. On Fri, Feb 02, 2018 at 05:01:25PM +, Simon Engelbert wrote: > We updated to the latest copr repo and it does not seem to make a difference, > we are seeing the exact same issues. > > We have noticed a weird pattern that

[SSSD-users] Re: SSSD/AD Issues After 1.14 to 1.15 upgrade in CentOS 7

We updated to the latest copr repo and it does not seem to make a difference, we are seeing the exact same issues. We have noticed a weird pattern that is, honestly, not always consistent but looks like this… ## Login attempt 1 ## *local* u...@domain.ad@local: ~$ ssh server Permission denied

[SSSD-users] Re: SSSD/AD Issues After 1.14 to 1.15 upgrade in CentOS 7

On (02/02/18 11:54), Jakub Hrozek wrote: >In the non-working cases, I see the name qualified where it shouldn't be >e.g: >[(&(sAMAccountName=u...@domain.ad)(objectclass=user)(sAMAccountName=*)(objectSID=*))][DC=DOMAIN,DC=AD]. > >while in the working case, the name in the filter is just