| |
| |
| |
|
Comments:
<0> Hello, I want to authenticate my networks (pc users) users against a ldap server, Can you recommend me a reading or how to ? In the web there are a lot of information is difficult make a filter of what I really need
<1> roche: http://enterprise.linux.com/enterprise/05/09/15/1930256.shtml?tid=129 gives a good tutorial for linux, were you looking for windows?
<0> koninkje, thanks, is for linux, Centos
<2> hm, I'm trying to configure phpLdapAdmin- and I'm wondering if there's a php4 equivalent of phpLdapAdmin I could use
<3> robert_: phpldapadmin should work on both php3 and php4 afaik
<2> 3 and 4?
<2> you mean 4 and 5?
<3> 3,4 and 5 I guess.. I don't have php5 running here
<4> Moin!
<4> I have a organizational unit with a mail adress? How would you solve that? Till now i put their name in the cn and sn field and use inetorgperson
<4> But that's sound a bit hacky and i'm sure that this cases must be also occur somewhere else
<4> And 'hello'! :)
<3> you could make your own auxiliary objectcl*** to support extended attributes and use objectcl*** organizationalUnit for OU-objects
<4> Sure, but i thought that this problem would be so common that somebody have thought of this
<3> I'm using such an extended objectcl*** to support my own set of attributes I want to set on OUs .. myCompanyOrgUnit .. MAY (mail,etc,etc)
<5> kanaldrache, isn't there rfc822recipient or similar auxilary objectcl*** ?
<5> I;ve seen an auxiliary objectcl*** mailRecipient
<6> hey, looking for some type of easy web interface for end users to search the ldap, also what is the procedure for changing the root dc's name, I did a test install with localdomain and would like to put it at the right name
<3> you can make a new one in slapd.conf and build it from scratch
<6> Gagatan: so I would have to basically make a whole new root and recreate the entries? that was what I was wondering
<3> jenocin: if you're changing from dc=localdomain to e.g. dc=adifferentdomain,dc=com - yes
<6> Gagatan: was figuring that... just wanted to make sure, I am using fedora ds, is it possible to have multiple roots with the same server instance
<3> it is with openldap - I don't remember with fedora ds
<7> jenocin: Yes. You can also get more fedora ds specific help on #fedora-ds
<6> k, thought they had a channel, but it looked empty, I'll try again
<6> still looking for a good way for my end users to use ldap, preferably web, any ideas?
<3> jenocin: for web, you have phpldapadmin, for gui - I suggest luma
<5> got this on restarting some of my slower slaves:
<5> bdb_db_open: last_id(/var/lib/ldap2.3/mail) failed: Cannot allocate memory (12)
<5> there is enough memory (2gb) for my 3 databases, each with 512MB cache configured
<8> is there anyone out there who uses hpux 11 against openldap 2.3.24?
<8> Or at least 2.3.x?
<2> does anybody have a clue how I configure phpldapadmin?
<2> is there a guide to configuring openldap on ubuntu?
<9> robert_: you may prefer to really learn openldap instead of following the countless guides that exist around there, and possibly incomplete?
<2> where do I st art, then? I have no idea how to configure openldap
<3> robert_: start with openldap.org quickstart-guide, admin-guide and faq-o-matic
<2> well, you may have just answered my question
<2> heh
<10> Hi! For some reason, when upgrading from (Debian's) OpenLdap version 2.2.26 to version 2.3.24, the slapd.conf option "schemacheck off" stopped working, why might that be?
<11> because schemacheck option was removed
<10> pfn: no replacement?
<11> no, schema is enforced
<10> That's kind of nasty.
<11> not really, anyway, check the mailing lists for the justification, it's brought up from time to time
<11> more or less, you don't necessarily need <specials> if you already have parent to contain them all
<10> pfn: I have no idea what you are talking about. Basically, we upgraded ldap because the old one was suddenly eating up the memory, and we had an ldap-outage of around 30 minutes because we had to fix all the things that didn't comply with the schemas :-\
<10> That's why I think it's sort of nasty to suddenly drop support of something that was operative in the previous version :-\
<3> "suddenly"
<3> schemacheck off should been allowed in the first place if you ask me
<3> at least it wasn't removed between 2.2.26 and 2.2.27 or something similar
<3> schemacheck good, schemacheck off nasty
<10> Gagatan: I get your point
<10> Gagatan: but when you have a working environment that breaks after an upgrade... You feel tricked.
Return to
#ldap
or
Go to some related
logs:
#kde
fsockopen permission debian
sudo linux keep environment
#linux
Blue-Steel Linux Keylogger
+mysql +connection pooling my.cnf -php
Python Concatenate List to String
#awk
chroot /mnt/sysimage input output error
python FindBin equivalent
|
|