openldap-technical

openldap-technical@openldap.org

20 participants
9802 discussions

backend meta rwm rewrite attribute value that is not DNs
by Nicolas RENAULT 03 Jul '14

03 Jul '14

Hello, Questions from this first post http://www.openldap.org/lists/openldap-technical/201407/msg00002.html I want to know if there is an overlay like rwm that can rewrite attribut values that are not DNs ? Exactly I want to rewrite createTimestamp (and all attribute that contains this datetime output form) value from yyyyMMddhhmmss.0Z to yyyyMMddHHmmssZ Regards -- Nicolas

1 0

Promoting slave to master LDAP server
by Bruno Furtado 03 Jul '14

03 Jul '14

Hi all, can I promote a LDAP slave server to master? Best regards, -- Bruno Furtado

2 1

Setting a flat to indicate disabled / enabled user
by Udai Singh Mehra (Vizury) 02 Jul '14

02 Jul '14

Hello, I am trying to develop a mechanism using which the users who left the organization can be easily identified and hence set their account as disabled. Is there any schema already available for this? I would appreicate if I can get to know anyone who has already encountered this situation and fixed the problem. Thanks. -- Udai Singh Mehra Infrastructure Engineering and Operations

2 3

rewrite of date-hour format from AD to openldap format
by Nicolas RENAULT 02 Jul '14

02 Jul '14

Hello, I have a openldap with meta backend connected to 3 ldap (one openldap, one edir and one AD). I test authentication again the proxy , it's working. my problem : dev team is working to use this proxy from alfresco, but there is error cause by date format on some attributes from Active Directory yyyyMMddHHmmss'.0Z' from OpenLDAP yyyyMMddHHmmss'Z' alfresco can understand only one type of date format on his configuration. (say dev team) they says to me : go to openldap format. so I want to rewrite all the attributes with date at yyyyMMddHHmmss'.0Z' to yyyyMMddHHmmss'Z' exemple : whenCreate (AD) to createTimestamp (openldap) I succesfully use rwm to rewrite DN but rwm-rewriteRule seem not to work for attributes that are not distinguishedname type. before asking I have googlize a lot without succes. any idea, clue or help ? Regards (sorry if bad english, I'm not fluent) -- Nicolas

2 2

Master Master or Master Slave Openldap replication.
by Kaushal Shriyan 01 Jul '14

01 Jul '14

Hi, Are there any document or writeup regarding setup of Master Master Openldap application? Do i need to go with setup of Master Master or Master Slave openldap replication, Please advice which approach should i follow and help me understand with some use cases. Regards, Kaushal

2 1

how to use ppolicy schema
by Udai Singh Mehra (Vizury) 30 Jun '14

30 Jun '14

Hi, I want to set password policies for my users in LDAP. Therefore i used the ppolicy.schema and added it to cn=config. I also used the ppolicy to be used as a olcOverLay Module. But I am unable to see a way to use it. I fail to create a default password policy for all the users. Can anyone send me some guidling steps as to how can I use the ppolicy.schema and set password policies for my users. i am using openldap in Ubuntu 14.04 which has everything set in slapd database. thanks, -- Udai Singh Mehra Infrastructure Engineering and Operations

1 0

LDAP limit of groups per user
by Julien Courtès 30 Jun '14

30 Jun '14

Hi, I am experiencing an issue with posix groups. I have a user which belongs to 28 posix groups but when I use the command "id" on the user, I can't see all the groups whereas as root, I can clearly see that this member belongs to much groups. Is there a limit of posix groups per user? If yes, how to increase it? Thanks Julien Courtès

2 2

zero copy jni lib for lmdb
by Kristoffer Sjögren 29 Jun '14

29 Jun '14

Hi I'm experimenting a bit with developing a JNI library for LMDB that utilize zero copy buffers. As you may know there is a project called lmdbjni [1] already but it does buffer copy only. I must admit that my C and JNI skills is not really that great, so please forgive any stupidity on my part. Anyway, i'm taking the sun.misc.Unsafe (no bounds checking) approach for memory allocation and pass memory addresses through JNI to LMDB for both writes and reads and at the moment I have implemented put, get, begin, commit [2]. I suspect that something is wrong because the performance between the buffer copy and zero copy isn't really that big. lmdbjni is even faster sometimes, write commits specifically is almost twice as fast. The test write 1M entries with a 4 bytes key (1-1M) and 128 bytes value (random) committed in one go. LMDB is configured identically both implementations with 4GB MDB_WRITEMAP. I run Linux 3.2.0 with Intel(R) Core(TM)2 Quad CPU Q6600 @ 2.40GHz. JProfiler show no signs of bottlenecks in Java in my implementation, most time is spent on the native methods put and commit. The opposite is true for lmdbjni where most time is spent creating and writing Java byte buffers, while native put and commit is just a fraction of that time. Not sure exactly the significance of the gcc compiler but here is how I do it. gcc -g -Wall -O2 -Wbad-function-cast -Wno-write-strings -fPIC -shared -I$JAVA_HOME/include -I$JAVA_HOME/include/linux -Isrc/main/native src/main/native/jlmdb.c src/main/native/liblmdb.a -o target/linux64/libjlmdb.so - What could be the reason for "slow(er)" commits? - How much faster can I expect properly implemented zero copying to be? - Maybe lmdbjni have defacto standard optimizations that me as a C noobie might have overlooked? - Are there any performance counters, tracepoints or similar that might be of interest to find where latency is spent? Greatful for any tips or pointers on how to track the problem down. Cheers, -Kristoffer [1] https://github.com/chirino/lmdbjni [2] JNI MDB_env *mdb_env; MDB_dbi dbi; JNIEXPORT jlong JNICALL Java_NativeLmdb_put (JNIEnv * env, jobject obj, jlong tx, jlong keyAddress, jlong keySize, jlong valAddress, jlong valSize) { MDB_val mdb_key, mdb_val; mdb_key.mv_data = (void *)(intptr_t) keyAddress; mdb_key.mv_size = (size_t) keySize; mdb_val.mv_data = (void *)(intptr_t) valAddress; mdb_val.mv_size = (size_t) valSize; int rc = mdb_put((MDB_txn *) (intptr_t) tx, dbi, &mdb_key, &mdb_val, 0); return rc; } JNIEXPORT jlong JNICALL Java_NativeLmdb_get (JNIEnv *env, jobject o, jlong tx, jlong a, jlong s) { MDB_val mdb_key, mdb_val; mdb_key.mv_data = (void *)(intptr_t) a; mdb_key.mv_size = (size_t) s; int rc = mdb_get((MDB_txn *) (intptr_t) tx, dbi, &mdb_key, &mdb_val); if (rc == 0) { return (intptr_t) mdb_val.mv_data; } return -1; } JNIEXPORT void JNICALL Java_org_deephacks_lmdb_NativeLmdb_mdb_1txn_1begin(JNIEnv *env, jobject obj, jlongArray array) { jlong *nArray = (*env)->GetLongArrayElements(env, array, NULL); MDB_txn *txn; mdb_txn_begin(mdb_env, NULL, 0, &txn); nArray[0] = (jlong) txn; (*env)->ReleaseLongArrayElements(env, array, nArray, 0); } JNIEXPORT void JNICALL Java_NativeLmdb_mdb_1txn_1begin(JNIEnv *env, jobject obj, jlongArray tx) { jlong *nArray = (*env)->GetLongArrayElements(env, array, NULL); MDB_txn *txn; mdb_txn_begin(mdb_env, NULL, 0, &txn); tx[0] = (jlong) txn; (*env)->ReleaseLongArrayElements(env, tx, nArray, 0); } JNIEXPORT jint JNICALL Java_NativeLmdb_mdb_1txn_1commit(JNIEnv *env, jobject obj, jlong tx) { return (jint)mdb_txn_commit((MDB_txn *)(intptr_t)tx); } JNIEXPORT void JNICALL Java_NativeLmdb_open (JNIEnv * env, jobject obj) { mdb_env_create(&mdb_env); mdb_env_set_mapsize(mdb_env, 4294967296); mdb_env_open(mdb_env, "/tmp/testdb", MDB_WRITEMAP, 0664); MDB_txn *txn; mdb_txn_begin(mdb_env, NULL, 0, &txn); mdb_open(txn, NULL, 0, &dbi); mdb_txn_commit(txn); }

2 3

Syncrepl and problem with ldap_sasl_bind_s failed?
by Eivind Olsen 27 Jun '14

27 Jun '14

Hello. I'm struggling a bit with setting up syncrepl replication between two OpenLDAP servers (using version 2.4.39 compiled by the LTB project, on top of RHEL6, if that matters in this case). Does anyone here have some suggestions on what I should look deeper into here? Is it a known newbie-error I'm making? I can post configuration files, describe how I attempt to set up the replication etc. The two servers have a replicated cn=config, in addition to two suffixes with their own HDB backend. The first of those suffixes are meant for administrative data, replication user account, etc., and the second suffix is for some end-user accounts/settings. I seem to have managed to get the first HDB backend to replicate, but I can't get the 2nd to work for some reason (most likely because I'm doing something wrong). When I start OpenLDAP with some debug logging, I see several log line, but the first ones that catches my interest looks like: 53ac30ff slapd starting 53ac30ff slap_client_connect: URI=ldap://ldap01-testing.aminor.no DN="cn=replicator,ou=admins,ou=internal,o=aminor" ldap_sasl_bind_s failed (49) 53ac30ff do_syncrepl: rid=005 rc 49 retrying (4 retries left) (this was seen on the node ldap02-testing.aminor.no. The hostnames exist in DNS internally, the two nodes can see each other on the IP level etc.) Both the working and non-working suffix are configured to use the same replication user (which lives in the 1st suffix). In my case, I have 2 hdb backends, one seems to replicate just fine, the other doesn't. I can use ldapsearch on the suffix for that non-replicating hdb from both nodes to both nodes, and get replies back (running ldapsearch -x, with -D and -w giving the cn=replicator,ou=admins...etc. and password). I went to the #openldap IRC channel and asked about this issue earlier today, and I saw another person ask about the same "ldap_sasl_bind_s failed (49)" error message as well. He was using a somewhat older OpenLDAP though (2.4.23) on Debian though. Regards Eivind Olsen

3 6

mdb maxsize too big - no specific error message?
by Marc Patermann 25 Jun '14

25 Jun '14

Hi, is there no specific error message if the mdb maxsize is too big (for the containing filesystem)? I used my ansible (great tool!) playbook to create an ldap server in a test VM. This was only 8 GB small. My initial slapadd failed and I did not why. (On my "real hardware" test machine this was all fine.) "mdb_db_open: cannot be opened, err 112, Restore from Backup!" If this is what "err 112" means, it should better say "maxsize too big" or something. It took me some time to figure out, my disk was to small for my config. Marc

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical