Re: use of ldap_str2dn()

Arthur de Jong wrote: I'm the maintainer of nss_ldapd [1] which is a replacement for nss_ldap. I have been trying to get rid of using deprecated functions while compiling with OpenLDAP 2.4.7. One of the changes I made was using ?ldap_str2dn() instead of ldap_explode_dn() and ldap_explode_rdn() t

Re: openldap and valgrind

Brian Hechinger wrote: I'm having an interesting time running my code through valgrind. Valgrind tell me this: ==31309== Conditional jump or move depends on uninitialised value(s) ==31309==at 0x4033004: ldap_first_attribute (in /usr/lib/libldap-2.3.so.0.2.15) ==31309==by 0x8053F45: lda

Re: Weird SASL thing

Rick Stevens wrote: I've created a fairly simple shell script that creates an appropriate LDIF file to add users to my database. It then calls "ldapadd" to add the user: RES=`ldapadd -U root -w $LDAPPWD -f $OUTFILE` However, when the script runs, the ldapadd is rejected with: ldap_sas

Weird SASL thing

First off, thanks for all the help on the CentOS 5 nsswitch.conf thing I ran into. I meant to reply to the thread, but I unfortunately deleted it from my mail client. It appears that "bind_type soft" did fix it, but I'm not certain (I can't reboot the server again to verify right now). However,

Re: Problems with openLDAP 2.3

Buchan Milne wrote: On Wednesday 26 March 2008 16:12:04 Admin wrote: Buchan Milne wrote: On Sunday 23 March 2008 18:44:00 Hallvard B Furuseth wrote: xjol0265 writes: We are upgrading our servers to RedHat 5.1, and in the process trying to migrate to openLDAP 2.3.27 (th

Re: smbk5pwd and ppolicy working together

Adam, Howard, and list, Upon Howard's suggestion, I went and re-read the docs on ACL's for slapd.conf. What I came up with is the following (I'll change the first asterisk to the specific attributes once I've actually got it working...): # ACL's access to * by dn.exact="cn=pwdchanger,dc=exam

openldap and valgrind

I'm having an interesting time running my code through valgrind. Valgrind tell me this: ==31309== Conditional jump or move depends on uninitialised value(s) ==31309==at 0x4033004: ldap_first_attribute (in /usr/lib/libldap-2.3.so.0.2.15) ==31309==by 0x8053F45: ldap_to_xmlrpc (mod_ldap.c:5

Re: Embedding Other LDAP Server in OpenLDAP for User Authentification [Virus checked]

[EMAIL PROTECTED] wrote: I've a tricky problem to solve. We are working with OpenLDAP 2.2.30. You should definitely upgrade your OpenLDAP installation since status of 2.2.x is historic. Which means there are no (security) updates anymore. Nada! The authentification-request which our LDAP

Re: Non-Ascii characters in certificateExactMatch

[EMAIL PROTECTED] wrote: Sorry for no info in last message. I have a certificate with non-ascii characters in it. Then i try to search this certificate there is no luck(but ok with others). Is it possible to encode no-ascii character to something that openldap can understand? Can you provide

use of ldap_str2dn()

I'm the maintainer of nss_ldapd [1] which is a replacement for nss_ldap. I have been trying to get rid of using deprecated functions while compiling with OpenLDAP 2.4.7. One of the changes I made was using ldap_str2dn() instead of ldap_explode_dn() and ldap_explode_rdn() to parse the DN of entrie

Embedding Other LDAP Server in OpenLDAP for User Authentification [Virus checked]

Hello, I've a tricky problem to solve. We are working with OpenLDAP 2.2.30. To improve the end user comfort we like to configure a special behavior of our LDAP. The authentification-request which our LDAP gets should first forwarded to an other LDAP server (primary LDAP). Just if the authentif

Re: Non-Ascii characters in certificateExactMatch

Sorry for no info in last message. I have a certificate with non-ascii characters in it. Then i try to search this certificate there is no luck(but ok with others). Is it possible to encode no-ascii character to something that openldap can understand?

Non-Ascii characters in certificateExactMatch

Is it possible?