openldap-technical

openldap-technical@openldap.org

4 participants
9898 discussions

I have 2 questions
by Haroon Rawat 21 Aug '12

21 Aug '12

Hi Experts, I have 2 questions currently using MDB and openldap-2.4.30 1. Slapadd is giving error *"Unrecognized database type (mdb)" *2. Ldapadd after inserting few records successfully then it start giving an error*. * 502a4151 mdb_id2entry_put: *mdb_put failed: Cannot allocate memory(12) "* subdata=pcsprof,msisdn=9800001823,dc=msisdn,dc=c-ntdb" 502a4151 conn=1000 op=1 RESULT tag=105 err=80 text=entry store failed * Waiting for the Ans.. Thanks * -- BR's, Haroon Rawat

3 5

Re: ldap (openldap) dynamic subtree combination for responses
by vlad florentino 21 Aug '12

21 Aug '12

I appreciate the answer. It's good to have a definitive answer.

1 0

ldap (openldap) dynamic subtree combination for responses
by vlad florentino 20 Aug '12

20 Aug '12

LDAP Server: OpenLDAP 2.4.24 Linux Distro: Fedora 15 (I believe this question is generally about returning properties in subentries, when performing searches on a parent entry, in a way that's transparent to clients making the requests. However, I have worded my question to be based on my specific usecase.) ------------------------------ Hi, I have successfully configure the Linux sssd service to fetch user loging information from an LDAP directory service (which happens to be in the same machine). The file to configure for this lives at /etc/sssd/sssd.conf I have tested that I can create a linux user account in the LDAP directory, by creating an entry under the relevant DN. That node includes the objectClass 'posixAccount'. ou=people | - uid=1000 # This entry has the objectClass 'posixAccount' performing a: getent passwd | grep the-ldap-based-linux-username yields correct information. Now, for my problem: I'm trying to configure the LDAP directory such that credentials information is not duplicated. I would like to define the entries like so: ou=people | - uid=1000 # No possixAccount objectClass | + cn=contact-info # contact stuff ... - cn=account # contains subtrees for account related stuff. | - cn=credentials # Fields: uid, userPassword, uidNumber, gidNumber - cn=linux-account # Fields: homeDirectory, loginShell, ... - cn=windows-account # Fields: winHomeDirectory, sambaServerUrl, ... - cn=samba-account # Fields: space-quota, ... The point of what I'm trying to accomplish is that when ldap clients, such as the Linux sssd deamon, perform an account info search/fetch, they do so at the following node (not at it's subnodes): cn=account,uid=1000,ou=people And that, somehow, the OpenLDAP server would know to combine the info contained in the relevant subentries of cn=account, and return those to the client, as if those extries existed at cn=account. This would work, of course, if I were to place all the info at the cn=account node. But, that's what I'm trying to avoid. I've try a few things, which have all been unsuccessful. Is it possible to do this with OpenLDAP (or LDAP in general)? If so, how? Regards, Vlad ------------------------------ PS: A trick that I've found useful, and which can help in the final solution to the problem, is that the sssd deamon allows one to configure the name of the 'posixAccount'-like objectClass that it should use to locate account info. I noticed that I can tell it do look for a certain class, say c-linux-account, which I then define as an empty auxilary class. The daemon will successfully find entries, which contain this class. Then, if those entries contain properties named uid, userPassword, homeDirectory, etc, it will use those properties for their values. So, I can add that property to cn=account, and the deamon will find that entry correctly. I just now have to tell OpenLDAP to combine the entries below that node, and return them in the query.

2 1

2.4.32: mdb stable enough?
by Karsten Heymann 19 Aug '12

19 Aug '12

Hi, I know this is difficult to answer, but is the mdb backend as it comes in 2.4.32 ready for a productive master-master setup with somewhat less tham 1mio entries? slapd-mdb(5) states it's an early release and that incompatible changes may occur, but on the other hand hdb changes disk format from time to time too. So, what are the opinions? The setup will be extensively tested, but if mdb should not be ready yet I could skip the tests and concentrate on hdb. Thanks, Karsten

3 6

LDAP authentication using Radius
by JET JETASIK 18 Aug '12

18 Aug '12

I am investigating 2 factor authentication in which mostly they are radius server actually. My problem is that most of my applications relying on LDAP auth only. I am trying to figure out on how to use openldap/contrib/slapd-modules/passwd/radius.c I did compile and successfully loaded it but not sure how to configure it. This is what I put into slapd.conf to load the module: moduleload pw-radius.so config="/etc/radius.conf" Firstly I couldn't figure out what exactly is the format of /etc/radius.conf (Mandatory items: Radius server IP& Share Secret) Secondly the format of userpassword scheme, {RADIUS}XXXXYYY@ZZZ ?? --- Jetasik (JET) Manager, Transniaga(Thailand)

5 13

Re: ldappasswd gives error ldap_sasl_interactive_bind_s: No such attribute (16)
by Dan White 17 Aug '12

17 Aug '12

Keeping replies on openldap-technical(a)openldap.org is recommended, since it gives you more eyes for your problem. >> On Thu, Aug 16, 2012 at 2:30 PM, Dan White <dwhite(a)olp.net> wrote: >>> On 08/16/12 14:06 -0700, Jeffrey Parker wrote: >>>>> I cannot seem to find anything helpful about this issue. I had it >>>>> working before when I first setup OpenLDAP and I have not changed >>>>> any settings since then. The only thing I can seem to find is >>>>> suggestion saying to use -x when running ldappasswd. When I use -x I >>>>> get the error below >>>>> >>>>> Result: Strong(er) authentication required (8) >>>>> Additional info: only authenticated users may change passwords >>>>> >>>>> >>>> If binding with -x, you'll need to provide a bind dn (-D) and a password. >>>> >>>> I am running OpenLDAP, I am not sure what version but it is somewhat >>>> new. >>>> >>>> The error messages is briefly discussed in the OpenLDAP Administrator's >>>> Guide (section H.17). >>>> >>>> Verify that you are able to bind to the server with 'ldapwhoami', with >>>> your credentials. Once that succeeds, verify that your entry contains >>>> a 'userPassword' attribute, and that the user you are binding with has >>>> the permissions to change it. >On Aug 17, 2012 9:08 AM, "Dan White" <dwhite(a)olp.net> wrote: >> On 08/16/12 15:32 -0700, Jeffrey Parker wrote: >> >>> The setup that I have is a bit strange, I am not using OpenLDAP to >>> authenticate operating system users. I am using it for other >>> authentication. The authentication works for usermin which I am using >>> as an interface to change passwords and for phpldapadmin, and for >>> Hudson continuous integration. That section that you mentioned in the >>> OpenLDAP Administrator's guide does not give any help it just says what >>> that means not any indication on what to do to fix it. As a side note >>> ldapwhoami does not work because I am not authenticated through ldap to >>> login to the computer. I can manually change the password in >>> phpldapadmin, but I need the users to be able to change their own >>> password which was working but now it is not working and I did not >>> change anything since the time that it was working. >> >> A cannot assist you with phpldapadmin or usermin. >> >> If you would like users to change their own passwords with the ldappasswd >> utility, then ldapwhoami is an acid test. Users must be able to >> authenticate to your ldap server before they can change their passwords for >> themselves. This is unrelated to how you, or your users, authenticate to >> the operating system. >> >> When password changes worked, what command (include command line >> parameters) did your users use? On 08/17/12 09:46 -0700, Jeffrey Parker wrote: >Usermin runs ldappasswd. The command-line options when it worked are the >same as I tried before, just ldappasswd. Users can authenticate without any >issue. Common ldappasswd examples include: for simple binds: ldappasswd -x -D "uid=jsmith,dc=example,dc=net" -W -s "new_password" for sasl binds: ldappasswd -Y digest-md5 -U jsmith -s "new_password" What are the contents of the following files, if they exist? /etc/ldap/ldap.conf (or your system's equivalent) $HOME/ldaprc $HOME/.ldaprc ./ldaprc Consult the manpages for ldap.conf and ldappasswd. -- Dan White

1 0

Re: ldappasswd gives error ldap_sasl_interactive_bind_s: No such attribute (16)
by Dan White 17 Aug '12

17 Aug '12

(Readding openldap-technical(a)openldap.org to the CC list) On 08/16/12 15:32 -0700, Jeffrey Parker wrote: >The setup that I have is a bit strange, I am not using OpenLDAP to >authenticate operating system users. I am using it for other >authentication. The authentication works for usermin which I am using as an >interface to change passwords and for phpldapadmin, and for Hudson >continuous integration. That section that you mentioned in the OpenLDAP >Administrator's guide does not give any help it just says what that means >not any indication on what to do to fix it. As a side note ldapwhoami does >not work because I am not authenticated through ldap to login to the >computer. I can manually change the password in phpldapadmin, but I need >the users to be able to change their own password which was working but now >it is not working and I did not change anything since the time that it was >working. A cannot assist you with phpldapadmin or usermin. If you would like users to change their own passwords with the ldappasswd utility, then ldapwhoami is an acid test. Users must be able to authenticate to your ldap server before they can change their passwords for themselves. This is unrelated to how you, or your users, authenticate to the operating system. When password changes worked, what command (include command line parameters) did your users use? >On Thu, Aug 16, 2012 at 2:30 PM, Dan White <dwhite(a)olp.net> wrote: > >> On 08/16/12 14:06 -0700, Jeffrey Parker wrote: >> >>> I cannot seem to find anything helpful about this issue. I had it working >>> before when I first setup OpenLDAP and I have not changed any settings >>> since then. The only thing I can seem to find is suggestion saying to use >>> -x when running ldappasswd. When I use -x I get the error below >>> >>> Result: Strong(er) authentication required (8) >>> Additional info: only authenticated users may change passwords >>> >> >> If binding with -x, you'll need to provide a bind dn (-D) and a password. >> >> >> I am running OpenLDAP, I am not sure what version but it is somewhat new. >>> It is running on Turnkey Linux (ubuntu 10.04 based) and is in a virtual >>> machine. >>> >> >> The error messages is briefly discussed in the OpenLDAP Administrator's >> Guide (section H.17). >> >> Verify that you are able to bind to the server with 'ldapwhoami', with your >> credentials. Once that succeeds, verify that your entry contains a >> 'userPassword' attribute, and that the user you are binding with has the >> permissions to change it. >> >> -- >> Dan White >> >> -- Dan White

1 0

slapd-meta doesn't continue with multiple uri's
by Liam Gretton 17 Aug '12

17 Aug '12

I've been trying to get slapd-meta to failover using multiple URIs but can't get it to work. Initially I was using 2.4.26, but having seen the report in ITS#7050 I've now built 2.4.32 but the problem is still there as far as I can tell. This bug was quashed in 2.4.29 according to the change log. In the example below, if host1 is not contactable at the point a search is performed, host2 will be contacted and the result returned correctly but ldapsearch then hangs indefinitely and the server's debug (level 1) output spews the following messages endlessly: ldap_sasl_bind ldap_send_initial_request ldap_int_poll: fd: 10 tm: 0 502a4634 conn=1001 op=1 <<< meta_search_dobind_init[0]=4 502a4634 conn=1001 op=1 >>> meta_search_dobind_init[0] Here's the relevant portion of slapd.conf: database meta suffix dc=local rootdn cn=administrator,dc=local rootpw secret network-timeout 3 uri ldap://host1:3268/ou=dc1,dc=local uri ldap://host2:3268/ou=dc1,dc=local uri ldap://host3:3268/ou=dc1,dc=local suffixmassage "ou=dc1,dc=local" "dc=example,dc=com" idassert-bind bindmethod=simple binddn="cn=proxyuser,dc=example,dc=com" credentials="password" idassert-authzfrom "dn.exact:cn=administrator,dc=local" Am I doing something wrong or has the bug described in ITS#7050 crept back in? -- Liam Gretton liam.gretton(a)le.ac.uk HPC Architect http://www.le.ac.uk/its IT Services Tel: +44 (0)116 2522254 University of Leicester, University Road Leicestershire LE1 7RH, United Kingdom

3 13

Status of rfc2307bis?
by Pierre Girard 17 Aug '12

17 Aug '12

Hello, When I look at the list of included schema with openldap (http://www.openldap.org/doc/admin24/schema.html#Distributed Schema Files) rfc2307bis isn't listed. What is the status of that schema, is it obsolete? If I understand correctly, it expired in 2009. Is that correct? What we want to do is setup an LDAP server only to put automount information, what would be the proper way of doing that, use the nis.schema? Any recommendation? Thanks for your help.

1 0

syncrepl and glued databases
by Uwe Werler 17 Aug '12

17 Aug '12

Hello List, is it OK to glue a database via replication from different suffixes together? What I tried: syncrepl rid=010 provider=ldap://master01 searchbase="dc=example,dc=com" keepalive=300:5:5 retry="10 10 300 10 600 +" binddn="cn=syncuser,dc=example,dc=com" bindmethod=simple schemachecking=off credentials=secret scope=sub attrs="*,+" type=refreshAndPersist syncrepl rid=020 provider=ldap://master02 searchbase="ou=glue1" keepalive=300:5:5 retry="10 10 300 10 600 +" binddn="cn=syncuser,dc=example,dc=com" bindmethod=simple schemachecking=off credentials=secret scope=sub type=refreshAndPersist attrs="*,+" suffixmassage="ou=glue2,dc=example,dc=com" syncrepl rid=030 provider=ldap://master03 searchbase="ou=glue2" keepalive=300:5:5 retry="10 10 300 10 600 +" binddn="cn=syncuser,dc=example,dc=com" bindmethod=simple schemachecking=off credentials=secret scope=sub type=refreshAndPersist attrs="*,+" suffixmassage="ou=glue2,dc=example,dc=com" This seems to work. Is this OK? Or should I use the traditional way with subordinate and glued databases? Background: this replica should be the sync master for a bunch of other hosts. Thanks for any hint. Regards Uwe

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical