All;

As an additional troubleshooting step, I altered the SearchUserPw configuration 
item to no longer work, and it does not switch to the error at line 192.

Is it possible that OTRS 6 isn't properly detecting a failed initial LDAP bind?

Thank you,

Dominic L. Hilsbos, MBA 
Director - Information Technology 
Perform Air International Inc.
dhils...@performair.com 
300 S. Hamilton Pl. 
Gilbert, AZ 85233 
Phone: (480) 610-3500 
Fax: (480) 610-3501 
www.PerformAir.com



-----Original Message-----
From: otrs [mailto:otrs-boun...@lists.otrs.org] On Behalf Of 
dhils...@performair.com
Sent: Tuesday, September 04, 2018 9:20 AM
To: otrs@lists.otrs.org
Subject: [otrs] Agent LDAP Issue

All;

As I mentioned last week, I'm setting up a new OTRS 6 instance.  I have 
experience running OTRS 5.

In my OTRS 5 instance, we have one agent backend linked to LDAP (Active 
Directory), and several Customer backends linked to LDAP (Active Directory).

For this new instance we'll have several agent backends, linked to LDAP (Active 
Directory), and we'll use the default behavior for Customers.

I've run into an issue where I least expected it, with the LDAP configuration.

Here's the message I'm getting:
ERROR: OTRS-CGI-64 Perl: 5.16.3 OS: linux Time: Tue Sep  4 08:59:56 2018

 Message: Search failed! 000004DC: LdapErr: DSID-0C09075A, comment: In order to 
perform this operation a successful bind must be completed on the connection., 
data 0, v1db1

 RemoteAddress: 10.2.59.1
 RequestURI: /otrs/agent.pl

 Traceback (31582):
   Module: Kernel::System::Auth::LDAP::Auth Line: 215
   Module: Kernel::System::Auth::Auth Line: 152
   Module: Kernel::System::Web::InterfaceAgent::Run Line: 248
   Module: 
ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_agent_2epl::handler 
Line: 40
   Module: (eval) (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
   Module: ModPerl::Registry::handler (v1.99) Line: 32

ERROR: OTRS-CGI-64 Perl: 5.16.3 OS: linux Time: Tue Sep  4 08:59:56 2018

 Message: No UserID found for '<username>'!

 RemoteAddress: 10.2.59.1
 RequestURI: /otrs/agent.pl

 Traceback (31582):
   Module: Kernel::System::User::UserLookup Line: 968
   Module: Kernel::System::Auth::Auth Line: 245
   Module: Kernel::System::Web::InterfaceAgent::Run Line: 248
   Module: 
ModPerl::ROOT::ModPerl::Registry::opt_otrs_bin_cgi_2dbin_agent_2epl::handler 
Line: 40
   Module: (eval) (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::run (v1.99) Line: 207
   Module: ModPerl::RegistryCooker::default_handler (v1.99) Line: 173
   Module: ModPerl::Registry::handler (v1.99) Line: 32

I find this odd, because the initial bind does seem to be occurring, i.e. the 
first bind error isn't being generated at line 192 of Auth::LDAP, and it 
doesn't seem to attempt to re-bind until line 308.

Does anyone have any pointers on what I might be missing here?

Thank you,

Dominic L. Hilsbos
Director - Information Technology 
Perform Air International Inc.
dhils...@performair.com 
300 S. Hamilton Pl. 
Gilbert, AZ 85233 
Phone: (480) 610-3500 
Fax: (480) 610-3501 
www.PerformAir.com


---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs
---------------------------------------------------------------------
OTRS mailing list: otrs - Webpage: http://otrs.org/
Archive: http://lists.otrs.org/pipermail/otrs
To unsubscribe: http://lists.otrs.org/mailman/listinfo/otrs

Reply via email to