Re: Ldap authentication

[Kevin Kelly <kck@xxxxxxx>]

On Jul 6, 2017, at 8:14 AM, Kevin Kelly <kck@xxxxxxx> wrote:

The first thing to correct could be the bind.  You should be binding with cn=Directory Manager.

[05/Jul/2017:05:38:01.814000145 -0400] conn=19 op=0 BIND dn="Directory Manager,dc=text,dc=in" authzid="(null)", invalid bind dn

On Jul 6, 2017, at 6:05 AM, Narendra Laga <Narendra.Laga@xxxxxxxxx> wrote:

Hi,

can any one help on below issue.

we are integrating 389-DS with cyberoam, while doing test connection we are facing below error.

Please check the below Ldap authentication errors and check for  the solution.

 

@ green color is anonymous, yellow color is error of admin integration

 

[05/Jul/2017:05:36:47.061794640 -0400] conn=18 fd=76 slot=76 connection from 192.168.1.xx to 192.168.1.xx

[05/Jul/2017:05:36:47.061901295 -0400] conn=18 op=0 BIND dn="" method=128 version=3

[05/Jul/2017:05:36:47.061967021 -0400] conn=18 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn=""

[05/Jul/2017:05:36:47.062430621 -0400] conn=18 op=1 UNBIND

[05/Jul/2017:05:36:47.062449012 -0400] conn=18 op=1 fd=76 closed - U1

[05/Jul/2017:05:38:01.813877357 -0400] conn=19 fd=76 slot=76 connection from 192.168.1.xx to 192.168.1.xx

[05/Jul/2017:05:38:01.814000145 -0400] conn=19 op=0 BIND dn="Directory Manager,dc=text,dc=in" authzid="(null)", invalid bind dn

[05/Jul/2017:05:38:01.814048128 -0400] conn=19 op=0 RESULT err=34 tag=97 nentries=0 etime=0

[05/Jul/2017:05:38:01.814627178 -0400] conn=19 op=1 UNBIND

[05/Jul/2017:05:38:01.814642192 -0400] conn=19 op=1 fd=76 closed - U1

[05/Jul/2017:05:38:59.609119006 -0400] conn=20 fd=76 slot=76 connection from 192.168.1.254 to 192.168.1.159

[05/Jul/2017:05:38:59.609238893 -0400] conn=20 op=0 BIND dn="Directory Manager,dc=text,dc=in" authzid="(null)", invalid bind dn

 

 

 

Thanks & Regards,

Narendra.Laga

---

From: Narendra Laga <Narendra.Laga@xxxxxxxxx>
Sent: Thursday, July 6, 2017 3:29 PM
To: 389-users@xxxxxxxxxxxxxxxxxxxxxxx
Subject: [389-users] Re: IIAP - Ldap authentication

 

Hi,

can any one help on below issue.

we are integrating 389-DS with cyberoam, while doing test connection we are facing below error.

Please check the below Ldap authentication errors and check for  the solution.

@ green color is anonymous, yellow color is error of admin integration

[05/Jul/2017:05:36:47.061794640 -0400] conn=18 fd=76 slot=76 connection from 192.168.1.xx to 192.168.1.xx

[05/Jul/2017:05:36:47.061901295 -0400] conn=18 op=0 BIND dn="" method=128 version=3

[05/Jul/2017:05:36:47.061967021 -0400] conn=18 op=0 RESULT err=0 tag=97 nentries=0 etime=0 dn=""

[05/Jul/2017:05:36:47.062430621 -0400] conn=18 op=1 UNBIND

[05/Jul/2017:05:36:47.062449012 -0400] conn=18 op=1 fd=76 closed - U1

[05/Jul/2017:05:38:01.813877357 -0400] conn=19 fd=76 slot=76 connection from 192.168.1.xx to 192.168.1.xx

[05/Jul/2017:05:38:01.814000145 -0400] conn=19 op=0 BIND dn="Directory Manager,dc=text,dc=in" authzid="(null)", invalid bind dn

[05/Jul/2017:05:38:01.814048128 -0400] conn=19 op=0 RESULT err=34 tag=97 nentries=0 etime=0

[05/Jul/2017:05:38:01.814627178 -0400] conn=19 op=1 UNBIND

[05/Jul/2017:05:38:01.814642192 -0400] conn=19 op=1 fd=76 closed - U1

[05/Jul/2017:05:38:59.609119006 -0400] conn=20 fd=76 slot=76 connection from 192.168.1.254 to 192.168.1.159

[05/Jul/2017:05:38:59.609238893 -0400] conn=20 op=0 BIND dn="Directory Manager,dc=text,dc=in" authzid="(null)", invalid bind dn

 

Thanks & Regards,

Narendra.Laga

Engineer, NOC Operations

Locuz Enterprise Solutions Ltd | Tel : +91- 4045004678

http://www.locuz.com

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx

_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx