Indeed, and that is certainly the case. I might drop the filter
altogether, but there are pseudousers in that same container with no
e-mail address that it would not make sense to validate...
Like I said, with this filter I and 'mnm' have logged in just fine, but
'ulh' fails, and I can't really s
t;
> -Matt
> --
> *From: *"Gerald Young"
> *To: *"User questions and discussions about OTRS."
> *Sent: *Friday, November 22, 2013 10:13:27 AM
>
> *Subject: *Re: [otrs] Svar: Re: LDAP stopped finding users
>
> My suggestion
ng"
To: "User questions and discussions about OTRS."
Sent: Friday, November 22, 2013 10:13:27 AM
Subject: Re: [otrs] Svar: Re: LDAP stopped finding users
My suggestion is to use the documentation of Net::LDAP to create a test perl
file connection ... if it works, OTRS should wo
ons and discussions about OTRS."
> *Sent: *Friday, November 22, 2013 9:42:09 AM
>
> *Subject: *Re: [otrs] Svar: Re: LDAP stopped finding users
>
> Matt, is it possible that the user has a workstation logon restriction? It
> happened to us that even if the user was in the D
ions about OTRS."
Sent: Friday, November 22, 2013 9:42:09 AM
Subject: Re: [otrs] Svar: Re: LDAP stopped finding users
Matt, is it possible that the user has a workstation logon restriction? It
happened to us that even if the user was in the DB and the authentication was
ok, with that restri
ons and discussions about OTRS."
> *Sent: *Friday, November 22, 2013 9:04:50 AM
> *Subject: *Re: [otrs] Svar: Re: LDAP stopped finding users
>
>
> Filter='(&(cn=ulh)(mail=*)) means ulh is a common name and has an
> email address in ldap.
>
> On Fri, Nov 22, 2013
tabase just in case but that didn't work either.
-Matt
- Original Message -
From: "Gerald Young"
To: "User questions and discussions about OTRS."
Sent: Friday, November 22, 2013 9:04:50 AM
Subject: Re: [otrs] Svar: Re: LDAP stopped finding users
Filter
Filter='(&(cn=ulh)(mail=*)) means ulh is a common name and has an
email address in ldap.
On Fri, Nov 22, 2013 at 9:01 AM, Martin Møller wrote:
> I'm seeing the same thing with at least one use here.
>
> I can log in just fine, as well as a few others, but one user who has tried,
> gets this error
I'm seeing the same thing with at least one use here.
I can log in just fine, as well as a few others, but one user who has tried,
gets this error.
I have checked all the attributes - they are fine. No different from the rest
of us.
It's the same LDAP backend as before.
On the OTRS 3.2 system,
