Thursday, October 5, 2023

[389-users] Re: err=19 in a BIND operation

On 10/5/23 14:58, Ciber Center wrote:
Hi team,    I'm getting an result err=19 in a BIND operation, Anyone knows why this can happen?    this is the connection trace    conn=2894185 fd=205 slot=205 connection from client_ip to server_ip  conn=2894185 op=0 BIND dn="uid=user1,o=applications,o=school,c=es" method=128 version=3  conn=2894185 op=0 RESULT err=19 tag=97 nentries=0 etime=0.000494384  conn=2894185 op=1 UNBIND  conn=2894185 op=1 fd=205 closed - U1    I understood that error code 19 occurs only in MOD operations, is it correct?

I agree, err=19 (LDAP_CONSTRAINT_VIOLATION) is likely the consequence of an internal MOD during a BIND. I would guess password policy or account policy.

You may enable internal operation logging (core and plugins) with

replace: nsslapd-plugin-logging  nsslapd-plugin-logging: on  -  replace: nsslapd-accesslog-level  nsslapd-accesslog-level: 260  -  replace: nsslapd-auditlog-logging-enabled  nsslapd-auditlog-logging-enabled: on  -  replace: nsslapd-auditfaillog-logging-enabled  nsslapd-auditfaillog-logging-enabled: on  

    Thanks in advance.  _______________________________________________  389-users mailing list --  To unsubscribe send an email to  Fedora Code of Conduct:  List Guidelines:  List Archives:  Do not reply to spam, report it:  

No comments:

Post a Comment