[rt-users] LDAP External Auth intermittent failure
Lush, Aaron
alush at scentral.k12.in.us
Thu May 5 10:49:14 EDT 2016
Would you please post your LDAP configuration in RT_SiteConfig.pm? Omitting
any sensitive information, of course.
Sincerely,
Aaron Lush
Network Administrator
South Central Community School Corporation
(219) 767-2266 ext. 1111
On Thu, May 5, 2016 at 8:15 AM, t s <zzzz67 at hotmail.com> wrote:
> Getting an intermittent "RT::Authen::ExternalAuth::LDAP::_GetBoundLdapObj
> Can't bind: LDAP_INVALID_CREDENTIALS 49" error very similar to:
> http://requesttracker.8502.n7.nabble.com/LDAP-External-Auth-intermittent-failure-td58611.html
> .
>
>
> <http://requesttracker.8502.n7.nabble.com/LDAP-External-Auth-intermittent-failure-td58611.html>
> LDAP External Auth intermittent failure - RequestTracker
> <http://requesttracker.8502.n7.nabble.com/LDAP-External-Auth-intermittent-failure-td58611.html>
> requesttracker.8502.n7.nabble.com
> LDAP External Auth intermittent failure. I'm using RT-4.2.7 installed from
> source, on ubuntu 14.04LTS. I've been trying to get the External Auth
> (0.23) extension ...
>
> Almost daily the External Auth will randomly start getting the binding
> error above and stop accepting LDAP logins, a simple restart of RT fixes
> the problem. I'm using External Auth 0.25 and RT 4.2.12. The only
> suggestion in the post above is to update RT but these are both recent
> stable versions.
>
>
> Anyone ran into this problem? Is it an RT_SiteConfig problem? I wouldn't
> think so since it works for around 24 hours and then stops. Could it be
> some kind of network connectivity problem?
>
> ---------
> RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
> * Washington DC - May 23 & 24, 2016
>
>
--
Email Confidentiality Notice: This email message, including all
attachments, is for the sole use of the intended recipient(s) and contains
confidential information. If you are not the intended recipient, you may
not use, disclose, print, copy or disseminate this information. Please
reply and notify the sender, delete the message and any attachments and
destroy all copies.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20160505/3d69c8ef/attachment.htm>
More information about the rt-users
mailing list