openldap-technical

openldap-technical@openldap.org

9897 discussions

openLDAP: LDAP and LDAP over TLS support at same time
by GOKUL G 28 Mar '18

28 Mar '18

Hi Team, We are developing a LDAP client in our application. For this we are using openLDAP software. One of our requirement is to support either LDAP or LDAPS (LDAP/TLS) , based on the end-user input at runtime. So, in our application we should have support for both LDAP & LDAPS APIs and we would be calling LDAPS API (ldap_tls_start_s) based on this runtime configuration or else normal LDAP API would be called. ISSUE: We are able to integrate openLDAP with our application and achieve LDAP or LDAP/TLS requirement separately. Since, the support for TLS in openLDAP is macro controlled (HAVE_TLS), at compile time itself its decided whether LDAP or LDAPs . And we are not able to take this decision at run-time. If we compile openLDAP software with HAVE_TLS and use it for normal ldapsearch, this ldap command is seen in trace as ldap message over SSL without any encryption. But not as normal LDAP message. So, we understand to achieve our requirement, we would either be required to change the macro control of TLS to run-time control in the openLDAP code. (But we are feeling not to do this for maintainability purpose) (or) Try to use 2 openLDAP libraries, one compiled with HAVE_TLS and another without HAVE_TLS. And take care in application side to call the respective API without causing any resolution issue. Can you please suggest whether there is any other approach currently available in openLDAP to support both LDAP and LDAP/TLS at the sametime. Regards, G Gokul

3 4

Re: slapadd not adding some of the roleoccupent entries
by Quanah Gibson-Mount 26 Mar '18

26 Mar '18

--On Monday, March 26, 2018 9:16 AM -0700 rammohan ganapavarapu <rammohanganap(a)gmail.com> wrote: > When i try to import using slapadd -f hdb.ldif, some of the entries in > sysadmin role are not getting import, not sure what should be the reason. > Actually hdb backend to hdb backend import also same behaviour if i > pre-create with above root schema and keep the other server in cluster > is running. If i dont pre-create schema or if i dont keep the other > server running in a cluster i dont see this issue. slapadd by default outputs an error and will not continue (unless -c is specified) when it has a problem adding an entry. You should provide the error encountered. I'd also note that you appear to be adding LDIF that is missing operational attributes. That will not work well if you're running in MMR and expect replication to work. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

OpenLDAP UTF8 values support
by Andre Rodier 23 Mar '18

23 Mar '18

Hello, I have started a small project to build a mail server, and the authentication / users list is based on OpenLDAP. I want to use international characters for the "secondary" email addresses but and OpenLDAP is complaining about it, as invalid syntax. I use the field otherMailBox field. I found a make-shift by storing the email address encoded in base64, but I therefore need to be sure any client will be able to read these base64 encoded email addresses. So far, Dovecot is fine, I am not sure yet about Postfix. Is there any limitation in OpenLDAP that would prevent some fields to be stored in UTF8 directly? I have noticed that the givenName and surname are automatically encoded in base64 when containing accents, so is it a standard practice? Thanks for your advices. https://github.com/progmaticltd/homebox Kind regards, André

4 5

LMDB on Ramdisk (tmpfs)
by Luca Foppiano 23 Mar '18

23 Mar '18

Dear everybody, I'm using one of your component (LMDB) via a java JNDI bindings implementation (https://github.com/deephacks/lmdbjni <https://github.com/deephacks/lmdbjni>) and I'm having an issue when I deploy my LMDB file on a tempfs filesystem in RAM. The issue do not occur when the LMDB files are stored on a "normal" filesystem. When the data is in the tempfs ramdisk all the allocated memory ends up being in the Dirty area (it has not been written back to the Filesytem). Here an example using the ramdisk: 7ce320000000-7cfc20000000 r--s 00000000 00:26 2459 /ramfs/nerd/data/db/db-en/entityEmbeddings/data.mdb Size: 104857600 kB Rss: 1255680 kB Pss: 1255680 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 0 kB Private_Dirty: 1255680 kB <--- Referenced: 1255680 kB Anonymous: 0 kB AnonHugePages: 0 kB Shared_Hugetlb: 0 kB Private_Hugetlb: 0 kB Swap: 0 kB SwapPss: 0 kB KernelPageSize: 4 kB MMUPageSize: 4 kB Locked: 0 kB VmFlags: rd sh mr mw me ms sd and here an example without: 7ca4fc000000-7cbdfc000000 r--s 00000000 fd:00 11154951 /data/workspace/shared/nerd-data/db/db-en/entityEmbeddings/data.mdb Size: 104857600 kB Rss: 838124 kB Pss: 838124 kB Shared_Clean: 0 kB Shared_Dirty: 0 kB Private_Clean: 838124 kB <---- Private_Dirty: 0 kB Referenced: 764872 kB Anonymous: 0 kB AnonHugePages: 0 kB ShmemPmdMapped: 0 kB Shared_Hugetlb: 0 kB Private_Hugetlb: 0 kB Swap: 0 kB SwapPss: 0 kB KernelPageSize: 4 kB MMUPageSize: 4 kB Locked: 0 kB VmFlags: rd sh mr mw me ms sd According to my understanding the memory is dirty when 1)there are open transactions, 2) the data has not been written back to the filesystem What I don't understand is why there is a difference between filesystem and ramdisk? Is there any reason? The application (listed above) is not writing on the lmdb, but just reading (using reading transaction). Thank you Luca

3 5

Re: Migrate from hdb/bdb to mdb backend.
by Quanah Gibson-Mount 22 Mar '18

22 Mar '18

--On Thursday, March 22, 2018 3:59 PM -0700 rammohan ganapavarapu <rammohanganap(a)gmail.com> wrote: > > Thank you! As an aside, I would note that OpenLDAP 2.4.46 was released today, and it contains multiple fixes for replication. ;) Fixed slapd syncrepl deadlock when updating cookie (ITS#8752) Fixed slapd syncrepl callback to always be last in the stack (ITS#8752) Fixed slapd CSN queue processing (ITS#8801) Fixed slapo-accesslog cleanup to only occur on failed operations (ITS#8752) (delta-sync specific) Fixed slapo-syncprov memory leak with delete operations (ITS#8690) Fixed slapo-syncprov to not clear pending operation when checkpointing (ITS#8444) Fixed slapo-syncprov to correctly record contextCSN values in the accesslog (ITS#8100) (delta-sync specific) Fixed slapo-syncprov not to log checkpoints to accesslog db (ITS#8607) (delta-sync specific) Fixed slapo-syncprov to process changes from this SID on REFRESH (ITS#8800) Fixed slapo-syncprov session log parsing to not block other operations (ITS#8486) --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: Migrate from hdb/bdb to mdb backend.
by Quanah Gibson-Mount 22 Mar '18

22 Mar '18

--On Thursday, March 22, 2018 3:50 PM -0700 rammohan ganapavarapu <rammohanganap(a)gmail.com> wrote: > > Quanah, > > > Rest of the config looks OK right? also i can replicate from hdb/bdb to > mdb as i described in previous email right? I am using > openldap-servers-2.4.44-5.el7.x86_64 Replication is a function of protocol, so yes, you can replicate from hdb/bdb to mdb. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: Migrate from hdb/bdb to mdb backend.
by Quanah Gibson-Mount 22 Mar '18

22 Mar '18

--On Thursday, March 22, 2018 3:12 PM -0700 rammohan ganapavarapu <rammohanganap(a)gmail.com> wrote: > olcSyncrepl: {0}rid=1 provider=ldap://ldapservertest01:10389/ > binddn="cn=manager,dc=example,dc=com" bindmethod=simple > credentials=dontshare searchbase="dc=example,dc=com" attrs="*,+" > type=refreshAndPersist retry="5 +" timeout=0 keepalive=5:5:5 > network-timeout=0 starttls=no filter="(objectclass=*)" scope=sub > schemachecking=off > olcSyncrepl: {1}rid=2 provider=ldap://ldapservertest02:10389/ > binddn="cn=manager,dc=example,dc=com" bindmethod=simple > credentials=dontshare searchbase="dc=example,dc=com" attrs="*,+" > type=refreshAndPersist retry="5 +" timeout=0 keepalive=5:5:5 > network-timeout=0 starttls=no filter="(objectclass=*)" scope=sub > schemachecking=off > olcSyncrepl: {2}rid=3 provider=ldap://ldapservertest03:10389/ > binddn="cn=manager,dc=example,dc=com" bindmethod=simple > credentials=dontshare searchbase="dc=example,dc=com" attrs="*,+" > type=refreshAndPersist retry="5 +" timeout=0 keepalive=5:5:5 > network-timeout=0 starttls=no filter="(objectclass=*)" scope=sub > schemachecking=off > olcSyncrepl: {3}rid=4 provider=ldap://ldapservertest04:10389/ > binddn="cn=manager,dc=example,dc=com" bindmethod=simple > credentials=dontshare searchbase="dc=example,dc=com" attrs="*,+" > type=refreshAndPersist retry="5 +" timeout=0 keepalive=5:5:5 > network-timeout=0 starttls=no filter="(objectclass=*)" scope=sub > schemachecking=off Remove the pointer back to itself on each server, so they stop trying to replicate from themselves, or use a URL with the serverID. Also, what version of OpenLDAP are you using? --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: Migrate from hdb/bdb to mdb backend.
by Quanah Gibson-Mount 22 Mar '18

22 Mar '18

--On Thursday, March 22, 2018 2:25 PM -0700 rammohan ganapavarapu <rammohanganap(a)gmail.com> wrote: > serverID 300 ldap://ldapserver300 > serverID 301 ldap://ldapserver301 >From the slapd.conf man page for serverID: "The fully qualified hostname of each server should be used in the supplied URLs." > And each of them have the same olcSyncrepl You fail to note the olcServerID setting for the MDB cluster. You fail to note the syncprov settings for any of the databases. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

Re: Migrate from hdb/bdb to mdb backend.
by Quanah Gibson-Mount 22 Mar '18

22 Mar '18

--On Wednesday, March 21, 2018 11:48 AM -0700 rammohan ganapavarapu <rammohanganap(a)gmail.com> wrote: > It seems data is getting replicate but i am seeing this message in ldap > logs. > > > 5ab27b63 dn_callback : entries have identical CSN (lot of them), i did > find some post regarding this but couldn't find any conclusion. It seems > like this message is because of node is trying to self replicate? can i > have same node information in "olcSyncrepl" config when i am only > replicating user database not config databse? You've not provided any information on your configurations, so one cannot really surmise anything about the validity of said configurations. --Quanah -- Quanah Gibson-Mount Product Architect Symas Corporation Packaged, certified, and supported LDAP solutions powered by OpenLDAP: <http://www.symas.com>

1 0

OpenLDAP: ACLs using sockname and DN?
by Norman Gray 22 Mar '18

22 Mar '18

Greetings. In OpenLDAP (2.4.45, on FreeBSD), I'm trying to constrain the access of a DN to an attribute, by giving a DN access only when the connection is made via a socket; but without success. I may just be looking for an example of correct use. What I'm trying is olcAccess: to attrs=userPassword by dn.base="uid=pwreset,ou=service,dc=example,dc=edu" sockname.exact="/var/run/openldap/ldapi" write (the idea is that the pwreset DN can be used by an automatic password-reset script, but that that DN will have that access only when the script is running on the same machine as the LDAP server). This `by` phrase appears to match the production in Sect. 8.3 of the OpenLDAP access control documentation, and the remark in slapd.access(5) that the items in the <who> field ‘may be specified in combination’. And indeed there are no syntax warnings generated. I'm presuming that the combination implies an AND rather than an OR – this isn't made explicit in the documentation. I can find no examples covering this in either OpenLDAP documentation or on the web. This stanza works when the sockname element is absent, suggesting that the configuration is otherwise working as I expect. When I try to write the userPassword attribute using this DN, I get an ldap_modify: Insufficient access (50) error. The OpenLDAP documentation doesn't (somewhat surprisingly) explicitly state what the effect of this sockname element is, and the slapd.access(5) page says, rather obliquely, that: > The statements peername=<peername>, sockname=<sockname>, > domain=<domain>, and sockurl=<sockurl> mean that the contacting host > IP (in the form IP=<ip>:<port> for IPv4, or IP=[<ipv6>]:<port> for > IPv6) or the contacting host named pipe file name (in the form > PATH=<path> if connecting through a named pipe) for peername, the > named pipe file name for sockname, the contacting host name for > domain, and the contacting URL for sockurl are compared against > pattern to determine access. Saying 'determine access' doesn't actually say very much. Have I completely misunderstood the point of this access specification, or is there another way to do this? Best wishes, Norman -- Norman Gray : https://nxg.me.uk

2 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