openldap-software February 2008

openldap-software@openldap.org

86 participants
94 discussions

Re: grant access on a attribute specific value
by Fabrice Eudes 17 Feb '08

17 Feb '08

Hi, thanks for your answer but my chiefs are not in a separate group; the directory looks like this: + dc=example,dc=com | --- ou=groups | | | --- cn=group_1 (objectClass = posixGroup, members by attribute "memberUid") | | ... | --- cn=group_i | --- ou=persons | --- uid=person_1 (objectClass ~ inetOrgPerson, groups by attribute "groupesTravail") | ... --- uid=person_j * posixGroup and memberUid(== users' uid) are compulsory to use the directory for typo3 authentification. * there is no posixAccount objectClass for the persons' entries as they have no login account on the server * I use a "groupesTravail" multivalued attribute instead of the standard gidNumber as my users may belongs to more than one group (of persons who work on the same theme) * the "chiefs" are the persons I want to grant write access to ou=groups, so they can add or delete a uid when a user registered or quit some group. Their groupesTravail attribute contains the value 1200. So, the filter behavior I am trying to get for the <who> clause is: (&(objectClass=inetOrgPerson)(groupesTravail=1200)) with hope that it is more clear, and hope that someone has a solution :-) thanks !

1 0

Dynlist query
by Guy Deleeuw 16 Feb '08

16 Feb '08

Hi all I have a small problem that require your advice. We try to query our ldap database from dynlist entries : We have a tree like : testGroup .... - member - manager group2 - member - manager ect.. Each member entry is a dynlist, which have a dynamic multivalued attribue : "ExoMemberShipMember" I have on our slapd.conf this line : dynlist-attrset ExoMemberShip ExoMemberShipURL ExoMemberShipMember Now, I start a ldapsearch to show if the dynamic attribute is correctly populated : root@nova:~# ldapsearch -x -LLL -b "ou=groups,ou=portal,ou=www,ou=Exo,o=Eurofer,c=be" -s sub "(&(&(objectClass=ExoMemberShip)(ExoMemberShipURL=*)))" dn: cn=member,ou=testGroup,ou=groups,ou=portal,ou=www,ou=Exo,o=Eurofer,c=be objectClass: ExoMemberShip objectClass: top cn: member description: member ExoMemberShipURL: ldap:///br=Internal,o=Eurofer,c=be??sub?(uid=*) ExoMemberShipMember: cn=Cassou-Mounat Dominique,br=Internal,o=Eurofer,c=be ExoMemberShipMember: cn=Caufriez Freddy,br=Internal,o=Eurofer,c=be .... .... dn: cn=member,ou=group2,ou=groups,ou=portal,ou=www,ou=Exo,o=Eurofer,c=be objectClass: ExoMemberShip objectClass: top cn: member description: member ExoMemberShipURL: ldap:///br=Internal,o=Eurofer,c=be??sub?(uid=*) ExoMemberShipMember: cn=Cassou-Mounat Dominique,br=Internal,o=Eurofer,c=be ExoMemberShipMember: cn=Caufriez Freddy,br=Internal,o=Eurofer,c=be ... ... All work fine, I can retrieve the two group entries. Now, I try to retrieve the group which have a particular member (ExoMemberShipMember): ldapsearch -x -LLL -b "ou=groups,ou=portal,ou=www,ou=Exo,o=Eurofer,c=be" -s sub "(&(&(objectClass=ExoMemberShip)(ExoMemberShipURL=*))(ExoMemberShipMember=cn=De Leeuw Guy,br=Internal,o=Eurofer,c=be))" And I receive an empty respond. Could you give me your advice about the feasibility of this kind of query ? Thanks in advance for your respond Guy

3 3

replication with filter "auxiliary object class"
by Keutel, Jochen 15 Feb '08

15 Feb '08

Hello, is it possible with OpenLDAP to use a filter objectclass=abc as filter for syncrepl when abc is an auxiliary object class? This would mean: - When an entry is created on the master with e.g. object class "country" the entry is NOT replicated. - Later, when you modify this entry by adding the auxiliary object class "abc", the entry will be replicated (added) to the consumer. - Later, when you modify this entry by deleting the auxiliary object class "abc", the entry will deleted from the consumer. Means: A MODIFY operation in LDAP (client ---> server) can result in an ADD or DELETE operation in the replication protocol (server ---> server). I ask this because I know at least one X.500 based product (using X.500 DISP for replication) which can't handle this situation ... Regards, Jochen.

2 1

GSSAPI auth missing?
by Pat Riehecky 15 Feb '08

15 Feb '08

I was about to configure kerberos connections to my test OpenLDAP system (2.4.7, debian sid packages) when I discovered an oddity.... # ldapsearch -x -b "" -s base -LLL supportedSASLMechanisms dn: supportedSASLMechanisms: CRAM-MD5 supportedSASLMechanisms: DIGEST-MD5 supportedSASLMechanisms: LOGIN supportedSASLMechanisms: PLAIN supportedSASLMechanisms: NTLM I don't see GSSAPI in the list. My searching of the doc and google has met with no real results. What must I do to get GSSAPI added as a supported mechanism? Pat

5 5

Restricted/controlled simple bind
by Tobias Franzén 14 Feb '08

14 Feb '08

Hi. Is there a way to have a more fine-grained restriction for simple binds rather than just On of Off? Maybe some ACL regexp? For instance I want to restrict simple bind possibilities to direct children of two or three OU groups, and furthermore I want to restrict the simple binds for the normal users to those with a {SASL} entry in their userPassword (or everyone if it cannot be specified separately). I'm using the option "password-hash {CLEARTEXT}" and don't want users without a userPassword like "{SASL}<uid>@REALM" to be allowed to do simple binds to the LDAP database. I have a Kerberos realm setup to handle passwords and saslauthd for the password check. Some applications that I have running are not kerberized. So I can't disable simple binds completely, since these applications still need to do simple binds for authentication. You might say that simple binds won't be possible if entries don't have a userPassword attribute, but I'd like some better reassurance. /Tobias

3 7

Re: openldap and tls
by Michael Ströder 14 Feb '08

14 Feb '08

Dave wrote: > When you say client i'm assuming your refering > to the ldap client, Yes. > configuration file /usr/local/etc/openldap/ldap.conf, Concerning what the server slapd requires to come from the client is configured in the server's configuration. >Michael Ströder wrote: >> See man 5 slapd.conf for learning about what option TLSVerifyClient >> means. You should take my advice more literally. I'm not inventing comments just for fun. Please first check TLSVerifyClient in your slapd.conf. Ciao, Michael.

4 3

openldap and tls
by Dave 14 Feb '08

14 Feb '08

Hello, I'm still having issues with tls, getting a openldap 2.4 client and server to talk tls to each other. If anyone has a sanitized working configuration i'd like to see it. I'm starting to wonder if i have to apply any security settings? I'm getting the below with tls now. Thanks. Dave. #/usr/local/libexec/slapd -d 5 -h ldap://0.0.0.0 @(#) $OpenLDAP: slapd 2.4.7 (Jan 20 2008 00:56:58) $ root@ldap1:/var/ports/basejail/usr/ports/net/openldap24-server/work/openldap-2.4.7/servers/slapdldap_pvt_gethostbyname_a: host=ldap, r=0daemon_init: ldap://0.0.0.0daemon_init: listen on ldap://0.0.0.0daemon_init: 1 listeners to open...ldap_url_parse_ext(ldap://0.0.0.0)daemon: listener initialized ldap://0.0.0.0daemon_init: 1 listeners openedldap_createslapd init: initiated server.bdb_back_initialize: initialize BDB backendbdb_back_initialize: Berkeley DB 4.6.21: (September 27, 2007)bdb_db_init: Initializing BDB database>>> dnPrettyNormal: <dc=davemehler,dc=com>=> ldap_bv2dn(dc=davemehler,dc=com,0)<= ldap_bv2dn(dc=davemehler,dc=com)=0=> ldap_dn2bv(272)<= ldap_dn2bv(dc=davemehler,dc=com)=0=> ldap_dn2bv(272)<= ldap_dn2bv(dc=davemehler,dc=com)=0<<< dnPrettyNormal: <dc=davemehler,dc=com>, <dc=davemehler,dc=com>>>> dnPrettyNormal: <cn=Manager,dc=davemehler,dc=com>=> ldap_bv2dn(cn=Manager,dc=davemehler,dc=com,0)<= ldap_bv2dn(cn=Manager,dc=davemehler,dc=com)=0=> ldap_dn2bv(272)<= ldap_dn2bv(cn=Manager,dc=davemehler,dc=com)=0=> ldap_dn2bv(272)<= ldap_dn2bv(cn=manager,dc=davemehler,dc=com)=0<<< dnPrettyNormal: <cn=Manager,dc=davemehler,dc=com>,<cn=manager,dc=davemehler,dc=com>>>> dnNormalize: <cn=Subschema>=> ldap_bv2dn(cn=Subschema,0)<= ldap_bv2dn(cn=Subschema)=0=> ldap_dn2bv(272)<= ldap_dn2bv(cn=subschema)=0<<< dnNormalize: <cn=subschema>matching_rule_use_init 1.2.840.113556.1.4.804 (integerBitOrMatch): matchingRuleUse: (1.2.840.113556.1.4.804 NAME 'integerBitOrMatch' APPLIES (supportedLDAPVersion $ entryTtl $ uidNumber $ gidNumber $mailPreferenceOption $ shadowLastChange $ shadowMin $ shadowMax $shadowWarning $ shadowInactive $ shadowExpire $ shadowFlag $ ipServicePort $ipProtocolNumber $ oncRpcNumber ) ) 1.2.840.113556.1.4.803 (integerBitAndMatch): matchingRuleUse: (1.2.840.113556.1.4.803 NAME 'integerBitAndMatch' APPLIES (supportedLDAPVersion $ entryTtl $ uidNumber $ gidNumber $mailPreferenceOption $ shadowLastChange $ shadowMin $ shadowMax $shadowWarning $ shadowInactive $ shadowExpire $ shadowFlag $ ipServic ePort $ipProtocolNumber $ oncRpcNumber ) ) 1.3.6.1.4.1.1466.109.114.2 (caseIgnoreIA5Match): matchingRuleUse: (1.3.6.1.4.1.1466.109.114.2 NAME 'caseIgnoreIA5Match' APPLIES ( altServer $ c$ mail $ dc $ associatedDomain $ email $ aRecord $ mDRecord $ mXRecord $nSRecord $ sOARecord $ cNAMERecord $ janetMailbox $ gecos $ homeDirectory $loginShell $ memberUid $ memberNisNetgroup $ ipHostNumber $ ipNetworkNumber$ ipNetmaskNumber $ macAddress $ bootFile $ nisMapEntry $ mailbox $ quota $maildrop $ mailsource $ virtualdomain $ virtualdomainuser $ defaultdelivery$ disableimap $ disablepop3 $ disablewebmail $ sharedgroup $ disableshared $mailhost ) ) 1.3.6.1.4.1.1466.109.114.1 (caseExactIA5Match): matchingRuleUse: (1.3.6.1.4.1.1466.109.114.1 NAME 'caseExactIA5Match' APPLIES ( altServer $ c$ mail $ dc $ associatedDomain $ email $ aRecord $ mDRecord $ mXRecord $nSRecord $ sOARecord $ cNAMERecord $ janetMailbox $ gecos $ homeDirectory $loginShell $ memberUid $ memberNisNetgroup $ ipHostNumber $ ipNetworkNumber$ ipNetmaskNumber $ macAddress $ bootFile $ nisMapEntry $ mailbox $ quota $maildrop $ mailsource $ virtualdomain $ virtualdomainuser $ defaultdelivery$ disableimap $ disablepop3 $ disablewebmail $ sharedgroup $ disableshared $mailhost ) ) 2.5.13.35 (certificateMatch): 2.5.13.34 (certificateExactMatch):matchingRuleUse: ( 2.5.13.34 NAME 'certificateExactMatch' APPLIES (userCertificate $ cACertificate ) ) 2.5.13.30 (objectIdentifierFirstComponentMatch): matchingRuleUse: (2.5.13.30 NAME 'objectIdentifierFirstComponentMatch' APPLIES (supportedControl $ supportedExtension $ supportedFeatures $ ldapSyntaxes $supportedApplicationContext ) ) 2.5.13.29 (integerFirstComponentMatch): matchingRuleUse: ( 2.5.13.29NAME 'integerFirstComponentMatch' APPLIES ( supportedLDAPVersion $ entryTtl$ uidNumber $ gidNumber $ mailPreferenceOption $ shadowLastChange $shadowMin $ shadowMax $ shadowWarning $ shadowInactive $ shadowExpire $shadowFlag $ ipServicePort $ ipProtocolNumber $ oncRpcNumber ) ) 2.5.13.27 (generalizedTimeMa tch): matchingRuleUse: ( 2.5.13.27 NAME'generalizedTimeMatch' APPLIES ( createTimestamp $ modifyTimestamp ) ) 2.5.13.24 (protocolInformationMatch): matchingRuleUse: ( 2.5.13.24 NAME'protocolInformationMatch' APPLIES protocolInformation ) 2.5.13.23 (uniqueMemberMatch): matchingRuleUse: ( 2.5.13.23 NAME'uniqueMemberMatch' APPLIES uniqueMember ) 2.5.13.22 (presentationAddressMatch): matchingRuleUse: ( 2.5.13.22 NAME'presentationAddressMatch' APPLIES presentationAddress ) 2.5.13.20 (telephoneNumberMatch): matchingRuleUse: ( 2.5.13.20 NAME'telephoneNumberMatch' APPLIES ( telephoneNumber $ homePhone $ mobile $pager ) ) 2.5.13.17 (octetStringMatch): matchingRuleUse: ( 2.5.13.17 NAME'octetStringMatch' APPLIES ( userPassword $ clearPassword ) ) 2.5.13.16 (bitStringMatch): matchingRuleUse: ( 2.5.13.16 NAME'bitStringMatch' APPLIES x500UniqueIdentifier ) 2.5.13.14 (integerMatch): matchingRuleUse: ( 2.5.13.14 NAME'integerMatch' APPLIES ( supportedLDAPVersion $ entryTtl $ uidNumber $gidNumber $ mailPreferenceOption $ shadowLastChange $ shadowMin $ shadowMax$ shadowWarning $ shadowInactive $ shadowExpire $ shadowFlag $ ipServicePort$ ipProtocolNumber $ oncRpcNumber ) ) 2.5.13.13 (booleanMatch): matchingRuleUse: ( 2.5.13.13 NAME'booleanMatch' APPLIES hasSubordinates ) 2.5.13.11 (caseIgnoreListMatch): matchingRuleUse: ( 2.5.13.11 NAME'caseIgnoreListMatch' APPLIES ( postalAddress $ registeredAddress $homePostalAddress ) ) 2.5.13.8 (numericStringMatch): matchingRuleUse: ( 2.5.13.8 NAME'numericStringMatch' APPLIES ( x121Address $ internationaliSDNNumber ) ) 2.5.13.7 (caseExactSubstringsMatch): matchingRuleUse: ( 2.5.13.7 NAME'caseExactSubstringsMatch' APPLIES ( serialNumber $ destinationIndicator $dnQualifier ) ) 2.5.13.6 (caseExactOrderingMatch): matchingRuleUse: ( 2.5.13.6 NAME'caseExactOrderingMatch' APPLIES ( serialNumber $ destinationIndicator $dnQualifier ) ) 2.5.13.5 (caseExactMatch): matchingRuleUse: ( 2.5.13.5 NAME'caseExactMatch' APPLIES ( supportedSASLMechanisms $ vendorName $vendor Version $ ref $ name $ cn $ uid $ labeledURI $ description $knowledgeInformation $ sn $ serialNumber $ c $ l $ st $ street $ o $ ou $title $ businessCategory $ postalCode $ postOfficeBox $physicalDeliveryOfficeName $ destinationIndicator $ givenName $ initials $generationQualifier $ dnQualifier $ houseIdentifier $ dmdName $ pseudonym $textEncodedORAddress $ info $ drink $ roomNumber $ userClass $ host $documentIdentifier $ documentTitle $ documentVersion $ documentLocation $personalTitle $ co $ uniqueIdentifier $ organizationalStatus $ buildingName$ documentPublisher $ ipServiceProtocol $ nisMapName $ carLicense $departmentNumber $ displayName $ employeeNumber $ employeeType $preferredLanguage ) ) 2.5.13.4 (caseIgnoreSubstringsMatch): matchingRuleUse: ( 2.5.13.4 NAME'caseIgnoreSubstringsMatch' APPLIES ( serialNumber $ destinationIndicator $dnQualifier ) ) 2.5.13.3 (caseIgnoreOrderingMatch): matchingRuleUse: ( 2.5.13.3 NAME'caseIgnoreOrderingMatch' APPLIES ( serialNumber $ destinationIndicator $dnQualifier ) ) 2.5.13.2 (caseIgnoreMatch): matchingRuleUse: ( 2.5.13.2 NAME'caseIgnoreMatch' APPLIES ( supportedSASLMechanisms $ vendorName $vendorVersion $ ref $ name $ cn $ uid $ labeledURI $ description $knowledgeInformation $ sn $ serialNumber $ c $ l $ st $ street $ o $ ou $title $ businessCategory $ postalCode $ postOfficeBox $physicalDeliveryOfficeName $ destinationIndicator $ givenName $ initials $generationQualifier $ dnQualifier $ houseIdentifier $ dmdName $ pseudonym $textEncodedORAddress $ info $ drink $ roomNumber $ userClass $ host $documentIdentifier $ documentTitle $ documentVersion $ documentLocation $personalTitle $ co $ uniqueIdentifier $ organizationalStatus $ buildingName$ documentPublisher $ ipServiceProtocol $ nisMapName $ carLicense $departmentNumber $ displayName $ employeeNumber $ employeeType $preferredLanguage ) ) 1.2.36.79672281.1.13.3 (rdnMatch): 2.5.13.1(distinguishedNameMatch): matchingRuleUse: ( 2.5.13.1 NAME'distinguishedNameMatch' APPLIES ( creatorsName $ modifiersName $s ubschemaSubentry $ entryDN $ namingContexts $ aliasedObjectName $dynamicSubtrees $ distinguishedName $ seeAlso $ member $ owner $roleOccupant $ manager $ documentAuthor $ secretary $ associatedName $dITRedirect ) ) 2.5.13.0 (objectIdentifierMatch): matchingRuleUse: ( 2.5.13.0 NAME'objectIdentifierMatch' APPLIES ( supportedControl $ supportedExtension $supportedFeatures $ supportedApplicationContext ) )slapd startup: initiated.backend_startup_one: starting "cn=config"config_back_db_openconfig_build_entry: "cn=config"config_build_entry: "cn=module{0}"config_build_entry: "cn=schema"config_build_entry: "cn={0}core"config_build_entry: "cn={1}cosine"config_build_entry: "cn={2}nis"config_build_entry: "cn={3}inetorgperson"config_build_entry: "cn={4}authldap"config_build_entry: "olcDatabase={-1}frontend"config_build_entry: "olcDatabase={0}config"config_build_entry: "olcDatabase={1}bdb"backend_startup_one: starting "dc=davemehler,dc=com"bdb_db_open: "dc=davemehler,dc=com"bdb_db_open: warning - no DB_CONFIG file found in directory/var/db/openldap-data: (2).Expect poor performance for suffix "dc=davemehler,dc=com".bdb_db_open: database "dc=davemehler,dc=com":dbenv_open(/var/db/openldap-data).slapd startingslap_listener_activate(6):>>> slap_listener(ldap://0.0.0.0)connection_get(10)connection_get(10): got connid=0connection_read(10): checking for input on id=0ber_get_nextber_get_next: tag 0x30 len 29 contents:ber_get_nextconn=0 op=0 do_extendedber_scanf fmt ({m) ber:do_extended: oid=1.3.6.1.4.1.1466.20037send_ldap_extended: err=0 oid= len=0send_ldap_response: msgid=1 tag=120 err=0ber_flush2: 14 bytes to sd 10connection_get(10)connection_get(10): got connid=0connection_read(10): checking for input on id=0TLS trace: SSL_accept:before/accept initializationTLS trace: SSL_accept:SSLv3 read client hello ATLS trace: SSL_accept:SSLv3 write server hello ATLS trace: SSL_accept:SSLv3 write certificate ATLS trace: SSL_accept:SSLv3 write certificate request ATLS trace: SSL_accept:SSLv3 flush dataTLS trace: SSL_accept:error in SSLv3 re ad client certificate ATLS trace: SSL_accept:error in SSLv3 read client certificate Aconnection_get(10)connection_get(10): got connid=0connection_read(10): checking for input on id=0TLS trace: SSL3 alert write:fatal:handshake failureTLS trace: SSL_accept:error in SSLv3 read client certificate BTLS: can't accept.TLS: error:140890C7:SSL routines:SSL3_GET_CLIENT_CERTIFICATE:peer did notreturn a certificate s3_srvr.c:2514connection_read(10): TLS accept failure error=-1 id=0, closingconnection_closing: readying conn=0 sd=10 for closeconnection_close: conn=0 sd=10^Cdaemon: shutdown requested and initiated.slapd shutdown: waiting for 0 threads to terminateslapd shutdown: initiated====> bdb_cache_release_allslapd destroy: freeing system resources.slapd stopped.

3 3

Re: syncrepl with more that one database
by Howard Chu 14 Feb '08

14 Feb '08

James Hartley wrote: > Howard, chill dude. Thanks for your help. But, there was a conflict > of opinion on this thread. > I have been around software long enough to know that software should > be deterministic. So lose the attitude if it bugs you so much to > answer questions maybe you should hand it off to someone else. > > Lose the attitude my man. It doesn't help anyone. What attitude are you referring to, exactly? I provided you with factual answers, not opinions. Facts don't have attitudes. If I were giving an opinion I would have said "IMO". Learn the difference between facts and opinions. If you don't like precise, direct answers, that's too bad. I don't have time to make up fluffy touchy-feely ones. As for leaving answers to someone else - usually I do (that silly lack of time thing). But when people answer with wrong information, then I have to step in. > james > > On Thu, Feb 14, 2008 at 1:33 AM, Howard Chu<hyc(a)symas.com> wrote: >> James Hartley wrote: >> > ok now I have two opinions. >> >> Software isn't operated on opinions. The facts are as I stated them. >> >> >> > Has any one successfully completed >> > replication of multiple backends. >> >> Thousands of times. >> >> >> > If so which answer is correct. >> > >> > use a separate rid for each backend on the same server OR >> > use only one rid for both backends on one server. >> >> Each rid in a server must be unique. >> >> >> > I noticed with my configuration ( only one rid for both backends on >> > one server ) does not appear to get the >> > indexes. entryCSN, entryUUID for the second database. >> >> rids have no effect on indexing. You must have something else wrong in your >> config. >> >> > I have not had time to test the other option, but if I could get an >> > answer from someone that has been there >> > and done that, I would save me a little time and effort. >> > >> > Thanks >> > >> > james >> > On Feb 11, 2008 7:42 AM, Quanah Gibson-Mount<quanah(a)zimbra.com> wrote: >> >> --On Saturday, February 09, 2008 7:12 PM +0000 Gavin Henry >> >> <gavin.henry(a)gmail.com> wrote: >> >> >> >>> Who is this Quanah guy who keeps coming out with the wrong info? ;) >> >> It was perfectly correct for James' configuration. ;) -- -- Howard Chu Chief Architect, Symas Corp. http://www.symas.com Director, Highland Sun http://highlandsun.com/hyc/ Chief Architect, OpenLDAP http://www.openldap.org/project/

1 0

Re: syncrepl with more that one database
by James Hartley 14 Feb '08

14 Feb '08

ok now I have two opinions. Has any one successfully completed replication of multiple backends. If so which answer is correct. use a separate rid for each backend on the same server OR use only one rid for both backends on one server. I noticed with my configuration ( only one rid for both backends on one server ) does not appear to get the indexes. entryCSN, entryUUID for the second database. I have not had time to test the other option, but if I could get an answer from someone that has been there and done that, I would save me a little time and effort. Thanks james On Feb 11, 2008 7:42 AM, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Saturday, February 09, 2008 7:12 PM +0000 Gavin Henry > <gavin.henry(a)gmail.com> wrote: > > > Who is this Quanah guy who keeps coming out with the wrong info? ;) > > It was perfectly correct for James' configuration. ;) > > > --Quanah > > -- > > Quanah Gibson-Mount > Principal Software Engineer > Zimbra, Inc > -------------------- > Zimbra :: the leader in open source messaging and collaboration >

3 2

Openldap stops responding after a while
by Amir Saad 13 Feb '08

13 Feb '08

I'm using OpenLDAP 2.3.30-5 on Debian 4 as a users database to replace flat files. I noticed that my clients sometimes fail to query the LDAP server and report 'Cannot bind .....(-1)', I think this error means they failed to reach the LDAP server, I checked the server and I can see it is running! I had to restart the slapd again to make it work as before. This issue happens frequently and each time I have to restart slapd to make it respond to my clients, what is wrong? I'm using ldaps with a self-signed certificate. Thank you Amir _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

openldap-software February 2008