openldap-technical

openldap-technical@openldap.org

9 participants
9868 discussions

SYntax for Proxy addresses and attribute to be defined for proxy addresess in LDIF file
by Meena Ram 09 Apr '10

09 Apr '10

Dear folks: If any one has the syntax for adding proxy addresses in the LDIF file along with the normal mail attribute that will be really appreciated if you can share the Syntax. Req: Sample LDIF file with proxy addresses along with mail attribute Cheers!!!!!!!!!! RAM

1 0

Re: Sample Large ldiff file to support 1K users
by Meena Ram 09 Apr '10

09 Apr '10

Dear folks: If any one has the syntax for adding proxy addresses in the LDIF file along with the normal mail attribute that will be really appreciated if you can share the Syntax. This is needed for an openldap set up. Req: Sample LDIF file with proxy addresses along with mail attribute Cheers!!!!!!!!!! RAM

1 0

Re: group in groups
by Chris Jacobs 08 Apr '10

08 Apr '10

You're thinking of dyngroups (Dynamic Groups). - chris Chris Jacobs, Systems Administrator Apollo Group | Apollo Marketing | Aptimus 2001 6th Ave Ste 3200 | Seattle, WA 98121 phone: 206.441.9100 x1245 | mobile: 206.601.3256 | fax: 206.441.9661 email: chris.jacobs(a)apollogrp.edu ----- Original Message ----- From: openldap-technical-bounces+chris.jacobs=apollogrp.edu(a)OpenLDAP.org <openldap-technical-bounces+chris.jacobs=apollogrp.edu(a)OpenLDAP.org> To: openldap-technical(a)openldap.org <openldap-technical(a)openldap.org> Sent: Thu Apr 08 02:10:48 2010 Subject: group in groups Hello list We use our Openldap with a lot of applications like apache, squid, samba ... What for us whould be very usefull is to define in ldap groups with users and other groups therin. Is this possible in Ldap or maybe with the nss-module ? I cant find any documentation. Thank you luis This message is private and confidential. If you have received it in error, please notify the sender and remove it from your system.

2 1

confusing manpage for slapcat for backup
by hai wu 08 Apr '10

08 Apr '10

I have some questions: When I look at manpage for slapcat from openldap-servers-2.3.27-5 in Centos5.0, it says: LIMITATIONS In general, your slapd(8) should not be running (at least, not in read- write mode) when you do this to ensure consistency of the database. But when I look at its manpage from openldap-servers-2.3.43-3.el5 in Centos5.4, it says: LIMITATIONS For some backend types, your slapd(8) should not be running (at least, not in read-write mode) when you do this to ensure consistency of the database. It is always safe to run slapcat with the slapd-bdb(5), slapd-hdb(5), and slapd-null(5) backends. Question 1: Is it always safe to run slapcat with slapd running even for openldap-servers-2.3.27-5 in Centos5? The administration guide for OpenLDAP 2.4 at http://www.openldap.org/doc/admin24/maintenance.html explains more on this, I quote: "2. Periodically run slapcat and back up the LDIF file: Slapcat can be run while slapd is active. However, one runs the risk of an inconsistent database- not from the point of slapd, but from the point of the applications using LDAP. For example, if a provisioning application performed tasks that consisted of several LDAP operations, and the slapcat took place concurrently with those operations, then there might be inconsistencies in the LDAP database from the point of view of that provisioning application and applications that depended on it. One must, therefore, be convinced something like that won't happen. One way to do that would be to put the database in read-only mode while performing the slapcat. The other disadvantage of this approach is that the generated LDIF files can be rather large and the accumulation of the day's backups could add up to a substantial amount of space. You can use *slapcat*(8) to generate an LDIF file for each of your *slapd*(8) back-bdb or back-hdb databases. slapcat -f slapd.conf -b "dc=example,dc=com" For back-bdb and back-hdb, this command may be ran while slapd(8) is running." Question 2: Is the above also true for openldap-servers-2.3.27-5 in Centos5? Question 3: How to put the database in read-only mode while performing the slapcat? Is there anyone who's doing this just to make sure for consistent backup? Thanks, Hai

3 2

Using "overlay dynlist" with Ubuntu Karmic 9.10 LDAP server using slapd.d (not slapd.conf) ?
by Shamika Joshi 08 Apr '10

08 Apr '10

Hi The desired implementation is to control user logins on different lab machines based on the project groups. Scenario: Bob is part of project group 'mars' & John is part of 'venus' then I have added lab machines x1-x3 to group 'mars' & y1-y3 to group venus. Now I want John to only access machines allocated for project 'mars' i.e x1 to x3 & John to access machines allocated for 'venus' i.e y1 to y3 I went through this link<http://www.hurricanelabs.com/september2009_login_security_using_openldap_an…>learned that it can be achieved using "overlay dynlist". Please correct me if I've got it wrong. However my lab server is Ubuntu 9.10 (karmic koala) and it is using slapd.d (not slapd.conf) So now if I want to attempt to use "overlay dynlist" how should I go about it? Has anyone done this before? Any help will be appreciated. Thanks Shamika

3 17

group in groups
by alois blasbichler 08 Apr '10

08 Apr '10

Hello list We use our Openldap with a lot of applications like apache, squid, samba ... What for us whould be very usefull is to define in ldap groups with users and other groups therin. Is this possible in Ldap or maybe with the nss-module ? I cant find any documentation. Thank you luis

2 1

password-hash
by Paul Soucy 08 Apr '10

08 Apr '10

Hi, I am running OpenLDAP 2.4 on Ubuntu 9.10. I am trying to get user passwords to be stored {SHA}. I understand the way to do this is by adding password-hash {SHA} line to the slapd.conf file. However, on Ubuntu 9.10 the /etc/slapd.conf is a directory not a file. What am I missing here?

3 2

openldap bug: libldap mutex hang on ldap_int_sasl_mutex
by Jeremiah Martell 07 Apr '10

07 Apr '10

After digging into this more, this definitely looks like a bug in openldap. I modified openldap to make all mutex's recursive. Then my GSSAPI rebind proc worked properly, and the search searched all referrals and found the result (two referrals later). Thanks, - Jeremiah ---------- Forwarded message ---------- From: Jeremiah Martell <inlovewithgod(a)gmail.com> Date: Mon, Mar 29, 2010 at 3:11 PM Subject: libldap mutex hang on ldap_int_sasl_mutex To: openldap-technical(a)openldap.org I'm using openldap-2.4.18, library libldap_r. I have three windows active directory servers setup: childA.parent.example.com parent.example.com childB.parent.example.com I do a LDAP+GSSAPI bind to childA.parent.example.com. The bind succeeds. I do a search that returns referrals, (I know I need to be referred to parent, and then childB in order to find my result), and I have openldap follow referrals for me. My rebind proc is a function that only calls: ldap_sasl_interactive_bind_s( ld, NULL, NULL, NULL, NULL, LDAP_SASL_AUTOMATIC, sasl_driver, params ); where sasl_driver and params is the same parameters that I used for the initial bind call to childA. After the seach call, the debug it looks like this: > ldap_chase_v3referrals, where ref[0] = parent.example.com > myGSSAPIrebindProc > ldap_sasl_interactive_bind_s < ldap_sasl_interactive_bind_s < myGSSAPIrebindProc < ldap_chase_v3referrals > ldap_chase_v3referrals, where ref[0] = childB.parent.example.com > myGSSAPIrebindProc > ldap_sasl_interactive_bind_s > ldap_chase_v3referrals, where ref[0] = childA.parent.example.com < ldap_chase_v3referrals > ldap_chase_v3referrals, where ref[0] = ForestDnsZones.parent.example.com > myGSSAPIrebindProc > ldap_sasl_interactive_bind_s ... HANG ON MUTEX Since this is hanging on a mutex, that would suggest a code bug. Perhaps the ldap_int_sasl_mutex needs to be a recursive mutex? Or should my rebind proc do something different than call ldap_sasl_interactive_bind_s? Any other ideas appreciated too. Thanks, - Jeremiah -- - Jeremiah Martell http://inlovewithGod.com

2 1

Partial replication
by Joe Friedeggs 07 Apr '10

07 Apr '10

Is it possible to replicate, on a slave, two branches of the DIT (only)? I have several instances of LDAP running on servers throughout the world. Connection to some of these from our support location is not dependable. I want to do something similar to this: Main LDAP (here, master): dc=example,dc=com | +--o=support | +--o=location_A | +--o=location_B | +--o=location_C In Location A (remote slave): dc=example,dc=com | +--o=support | +--o=location_A In Location B (remote slave): dc=example,dc=com | +--o=support | +--o=location_B Location A & B are two different customers, therefore it would not be prudent to replicate Location B's users in Locations A. But I need the Support group to exist in all locations. Can this be done using syncrepl? Another thought is to have LDAP Masters existing in each location, and somehow replicate the Support branch to each (mirrormode?). Should this be the approach? Thanks, Joe _________________________________________________________________ Hotmail has tools for the New Busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:…

4 10

RE: Partial replication
by Joe Friedeggs 06 Apr '10

06 Apr '10

The e-mail thread seems to have wandered a bit, hoping I am replying to the correct one. I've tested both methods, ACL vs 'syncrepl search filter', both seem to work well for me. I agree with Andrew's point that controlling this via the ACLs on the provider is more secure (in my case). Thanks for all the help and insight. Joe ---------------------------------------- > On Thu, Apr 01, 2010 at 09:53:07PM +0200, Zdenek Styblik wrote: > >>>> you want to replicate. So, let's say you use cn=mirrorA,dc=domain,dc=tld >>>> for replication, then allow this cn=mirrorA to read only >>>> o=support,dc=example,dc=com and o=location_A,dc=example,dc=com, but nowhere >>>> else. >>> >>> I have used that technique for a fairly complex design with a central >>> office and many small satellites. It works OK *provided* you never change >>> the list of entries that can be seen by the replicas. The syncrepl >>> system has no way to evaluate the effect of an ACL change (and probably >>> no way to know that one has happenned). >>> >> >> Could you please elaborate more on this one? > > My design requirements were similar to Joe's: I had a large central > server holding the master data for a lot of customers. Each customer > needed a local replica of their own data plus some subset of the > service-provider data. In my case the subset was not even complete > subtrees: the customers were allowed to see certain attributes of > certain entries only. I had to protect against the possibility that > someone might modify the config on a customer server to obtain data > that they should not have. > > As there was already a comprehensive default-deny access-control > policy in place, I just factored in the replica servers as principals > with the right to see all data that should be replicated to that site > and nothing else. That meant that every replica server could have an > identical syncrepl clause which just copies everything it can see from > the entire DIT. > > The downside is that if any access permissions change then the > replicas may not reflect the correct new subset of data. > >> Because I'd say if you refuse >> access later to some DN then it must be like DN has been deleted. Same goes >> for adding. I mean, syncrepl won't see data. And it checks, well it should >> check, for changes in some regular intervals, right? > > The problem is that syncrepl does not check every entry exhaustively. > That would be very inefficient (though I would like a way to force it > periodically). The master server maintains something like a timestamp > on the whole DIT, and when the replica server connects they just have > to compare timestamps and transfer things that have changed in the > interval between the two. (This is a gross simplification of the > actual protocol, but close enough for the discussion). > > Now imagine that I change an ACL which affects the visibility of some > entries. The entries themselves have not changed, so the timestamps do > not change and the replication process will not know that the replica > data should change. > > Worse still, I might change the membership of a group that is > referenced in an ACL. The replication process would transfer the group > but would not know that some other entries have changed visibility. > >> I have no need for nor experience with this, yet it's somewhat interesting. > > It is a powerful technique, but the designer *and operators* of such a > system must be aware of the pitfalls. > >> ACLs of anykind in OpenLDAP are kinda ... PITA, no offense to anybody!!! :) >> It just needs a lot of work to maintain and stuff (please please, no >> bashing). > > ACLs of any kind in any system (LDAP, file system, RDBMS etc) can be > hard to get right and harder to modify correctly at a later date. It > all depends on the policy that you are trying to implement. You should > think of ACLs as programs and expect to need programmer-level skill to > work on them. You may find this paper helpful: > > http://www.skills-1st.co.uk/papers/ldap-acls-jan-2009/ > > Of all the LDAP servers that I have worked with, I find OpenLDAP's > ACLs are the easiest for implementing non-trivial policies. > > Andrew > -- _________________________________________________________________ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:…

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