openldap-technical

openldap-technical@openldap.org

14 participants
9796 discussions

insert utf-8 data with c api
by yvan vander sanden 09 May '15

09 May '15

Hello. I have trouble inserting data in openldap when it contains utf8 characters. My code works as long as only ascii characters are present, but when a name has an accent or umlaut in it, the modify operation fails with an operations error. Even reading a string with such a character from an existing entry and pushing the same string back to ldap with ldap_modify_ext_s gives me this error. And while debugging I can see that the string in question really contains the correct uft8 values. Are there perhaps any options that have to be enabled? The only one I am using now is: int version = LDAP_VERSION3; ldap_set_option(_server, LDAP_OPT_PROTOCOL_VERSION, &version); Regards, yvan vander sanden -- ==- yvan vander sanden -== * composer, programmer * >>> http://mutecode.com -* MUTE software development* >>> http://attr-x.net - *online interactive soundscape* >>> http://code.google.com/p/yse-soundengine/ - *advanced 3D sound engine* >>> http://youngmusic.org - *personal website* >>> http://www.matrix-new-music.be/componist/vander-sanden-yvan-1972 - *bio @ matrix* <http://youngmusic.org>

1 0

Data is not getting replicated correctly in multimaster configuration
by Gurjot Kaur 08 May '15

08 May '15

Hi, I have configured two instances of LDAP in multimaster mode. I am creating 100 members and wait for 5 seconds and then deleting those 100 members. In case of creation the data is getting replicated correctly. But in deletion, all the 100 members are getting deleted from primary, but not from secondary server. As a result the data is inconsistent in both the instances. Please give any suggestion. Thanks and Regards, Gurjot Kaur Sofware Engineer gurjot.kaur(a)aricent.com [http://static.johnmcneilstudio.com/aricent/email_signature/aricent-footer-e…] "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error, please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus."

5 13

large write amplification
by Shu, Xinxin 07 May '15

07 May '15

Hi list, Recently I run micro tests on LMDB on DC3700 (200GB), I use bench code https://github.com/hyc/leveldb/tree/benches , I tested fillrandsync mode and collected iostat data, found that write amplification is large For fillrandsync case: IOPS : 1020 ops/sec Iostat data shows that w/s on that SSD is 8093, and avgqu-sz is ~ 1, await time is about 0.16 ms, so the write amplification is ~8, which is large to me, can someone help explain why write amplification is so large? thanks Cheers, xinxin

3 7

olcAuthzRegexp not matching
by Brendan Kearney 06 May '15

06 May '15

i am trying to get kerberos id <--> ldap object mapping down for dovecot, and seem to have hit a wall. i have the kerberos service principal created and a keytab populated. i can successfully kinit using the keytab and get a TGT for the imap/test.bpk2.com(a)BPK2.COM id. when i run ldapwhoami i get: SASL/GSSAPI authentication started SASL username: imap/test.bpk2.com(a)BPK2.COM SASL SSF: 56 SASL data security layer installed. dn:uid=imap/test.bpk2.com,ou=domainusers,ou=users,dc=bpk2,dc=com the olcAuthzRegexp i am trying to use is not matching and the mapping falls through to the regular user mappings. i have tried all the permutations i can thing of in the RegEx, but cannot get the match to occur. as a reference, i looked at the matching i do for the computer accounts, and there is nothing obviously wrong. olcAuthzRegexp attempts: {2}uid=imap\/(.*).bpk2.com,cn=bpk2.com,cn=gssapi,cn=auth uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com {2}uid=imap\/(.*),cn=bpk2.com,cn=gssapi,cn=auth uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com {2}uid=imap\/(.*),cn=gssapi,cn=auth uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com {2}uid=imap\/(.*),cn=auth uid=mda,ou=processUsers,ou=Users,dc=bpk2,dc=com klist output: Ticket cache: KEYRING:persistent:0:0 Default principal: imap/test.bpk2.com(a)BPK2.COM Valid starting Expires Service principal 05/06/2015 11:42:08 05/07/2015 11:40:16 ldap/server2.bpk2.com(a)BPK2.COM renew until 05/13/2015 11:40:16 05/06/2015 11:40:16 05/07/2015 11:40:16 ldap/server1.bpk2.com(a)BPK2.COM renew until 05/13/2015 11:40:16 05/06/2015 11:40:16 05/07/2015 11:40:16 krbtgt/BPK2.COM(a)BPK2.COM renew until 05/13/2015 11:40:16 how do i find what i am doing wrong? note the below olcAuthzRegexp works to map hosts to computer accounts: {0}uid=host\/(.*).bpk2.com,cn=bpk2.com,cn=gssapi,cn=auth cn=$1,ou=Computers,dc=bpk2,dc=com thanks, brendan

3 5

Openldap Replication issues
by PRATIK SINGAL 06 May '15

06 May '15

Hello all, I have installed openldap on two machines and tried to setup multi-way replication.I am able to perform the multi-way replication (Add/Update/delete) when both the machines are up and ldap is running. But when my one machine goes down(server2) and records are added,deleted,modified on (server1) are not getting replicated on server2 when its is up and ldap service is running. **Below are the machine on which ldap is installed:** [root@localhost openldap]# cat /etc/*-release LSB_VERSION=base-4.0-amd64:base-4.0-noarch:core-4.0-amd64:core-4.0-noarch:graphics-4.0-amd64:graphics-4.0-noarch:printing-4.0-amd64:printing-4.0-noarch Red Hat Enterprise Linux Server release 6.4 (Santiago) Red Hat Enterprise Linux Server release 6.4 (Santiago) **Openldap version:** [root@localhost openldap]# slapd -V @(#) $OpenLDAP: slapd 2.4.23 (Oct 31 2012 08:14:14) $ mockbuild@x86-022.build.eng.bos.redhat.com:/builddir/build/BUILD /openldap-2.4.23/openldap-2.4.23/build-servers/servers/slapd Attaching the complete logs and conf file used. Kindly let me know where am making mistake Regards, Pratik

2 1

About RDN values starting with #
by Pofelski, Lech 06 May '15

06 May '15

Hello openLDAP gurus, According to the RFC 4514, an RDN value may start with # and to be followed by a number of "hex pair" (pairs of hexadecimal values), representing octets of some binary value. There are two use cases involving such RDN syntax: · Case 1, where the RDN is of the form: <attribute OID (called also as attribute desc in dotted form)>=#<BER encoded attribute value in form of a sequence of hex pairs > · Case 2, where the RDN is of the form: <attribute name>=#<attribute value in form of a sequence of hex pairs> Case 1 is explicitly illustrated in the RFC 4514 by the example: 1.3.6.1.4.1.1466.0=#04024869 Although Case 2 is not explicitly illustrated in the RFC4514, it is implicitly correct, as it is in the conformity with the RDN syntax provided by this RFC. The example of Case2 equivalent to the example of Case1 given in the RFC would be: <name of the attribute with OID 1.3.6.1.4.1.1466.0>=#4869 I have tested using openLDAP 2.4.39 a number of cases involving RDNs starting with #, including an example very close to the example from the RFC. The results show that: · If RDN value is provided as e.g. string value, LDAP operations like add, search and delete work well · If RDN value is provided as # prefixed hexadecimal value corresponding to the cases 1 and 2, none of this cases work and in all the cases I get the error "Invalid DN syntax" The schema file, scripts used to run the test and the test results are in the attached zip file. I would like to know: · If you share our understanding of the problem and in particular our interpretation of the Case2, for which there is no explicit example in the RFC4514. · If this is a known limitation in openLDAP. · If there is already a plan to fix the problem. If not, I'd be glad to contribute to fixing it. Thanks in advance for your answer. Regards, Lech POFELSKI Lech POFELSKI, Software Development Engineer Hewlett-Packard Centre de Compétences France 5 Avenue Raymond Chanas 38320 Eybens - France lech.pofelski(a)hp.com<mailto:lech.pofelski@hp.com>

2 6

HP-UX: mdb_txn_commit and MDB_WRITEMAP
by Kristian Amlie 06 May '15

06 May '15

We have enabled MDB_WRITEMAP on our HP-UX 11.23 Itanium after previous discussions on the list, and that worked nicely for the most part. However now we face a different issue: Occasionally, mdb_txn_commit will return "Resource temporarily unavailable". I have not been able to determine exactly which resource it's talking about; I suspected shared memory limits, but raising this limit did not solve the problem. This issue did not occur without MDB_WRITEMAP. Any idea what else it could be? I can probably insert debug code into LMDB if that's needed. -- Kristian

2 2

RE24 testing call (2.4.41)
by Quanah Gibson-Mount 05 May '15

05 May '15

If you know how to build OpenLDAP manually, and would like to participate in testing the next set of code for the 2.4.41 release, please do so. Generally, get the code for RE24: <http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=snapshot;h=refs/h…> Configure & build. Execute the test suite (via make test) after it is built. Thanks! --Quanah -- Quanah Gibson-Mount Platform Architect Zimbra, Inc. -------------------- Zimbra :: the leader in open source messaging and collaboration

5 6

Need migrationhelp for 1.3.6.1.4.1.1466.115.121.1.5 because of bug in slapcat
by Frank Offermanns 05 May '15

05 May '15

Hello, in our custom schema we have used several attributes with the syntax: 1.3.6.1.4.1.1466.115.121.1.5 attributetype ( myAttributeType:106 NAME ( 'casFileContent' ) DESC 'Contains the file' SYNTAX 1.3.6.1.4.1.1466.115.121.1.5 SINGLE-VALUE ) We defined this schema before this syntax was dropped. Everything worked for a long time. Now with OpenLDAP Version 2.4.39 and newer a slapcat does no longer export this attributes as MimeContent, but as plain text. So the ldif can't be used for importing. So I started a research why and found that this syntax was dropped. But for downward compatibility shouldn't it still export this syntax as mime content, shouldt it? This would be important, since in inetorgperson.schema the 2 attributes userSMIMECertificate and userPKCS12 still use it. What syntax should I use for files stored in LDAP? And even more important, how can I change the syntax of a attribute. Is there a migration strategy to change the syntax of a attribute? Regards, Frank

4 10

Fast key range iteration
by Александр Киранов 05 May '15

05 May '15

Hi all! Is there a way to iterate with all key-value pairs in LMDB database, where all keys is in specified range? I'm trying to use mdb_cursor_get() with MDB_SET_RANGE to search first pair. Then I see only one way - use mdb_cursor_get() with MDB_NEXT and compare key by memcmp(). But it seems absolutely not effective. Is there another solution for my task? Thanks!

3 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical