On Fri, Aug 18, 2017 at 01:04:37PM -0400, Mark London wrote:
> Hi - The old server is gone, so I can't test it. Yes, the DN contains a
> space and comma for everybody, i.e. last name, first name.
Right, but then it doesn't constitute a pattern of failing users vs.
passing users right?
>
> I mig
Hi - The old server is gone, so I can't test it. Yes, the DN contains a
space and comma for everybody, i.e. last name, first name.
I might consider building SSSD from the source, to have it print out the
password. Strangely, the problem has at least temporarily abated.
That could be simp
Hmm, but I'm really not sure how to debug this. You said you only see
this with a new server. When you look at the logs from the working and
the non-working server, are there any differences?
For example, I see that the user's DN contains a space and a comma. Does
the issue only happen with these
No, sorry. Can't be incorrect passwords. The people aren't even typing in
their passwords. These are connections being made by email clients constantly
running. Different platforms and email clients. 🙁
Sent from my iPhone
> On Aug 18, 2017, at 4:05 AM, Jakub Hrozek wrote:
>
>> On Thu, Aug
On Thu, Aug 17, 2017 at 10:04:08PM -0400, Mark London wrote:
> Hi all - Sorry to bother you with this problem that I've been working all
> day to fix.I've been using SSSD on Redhat for many years, using LDAP to
> authenticate a Windows domain. With a new server with Redhat 7, I'm seeing
> int
