openldap-technical

openldap-technical@openldap.org

21 participants
9802 discussions

Start a nNew thread

problem with pwdReset
by Cyril Grosjean 04 Jul '11

04 Jul '11

2 1

cn=config and plugins
by Hanns Mattes 03 Jul '11

03 Jul '11

Hi, I'm interested in using the slapi-dnsnotify-plugin to notify slaves of changes in the pdns-server. There's an example configuration using slapd.conf[1], but I'd like to know how a plugin is configured using cn=config. Distribution ist Opensuse 11.3 zypper info shows: Name: openldap2 Version: 2.4.21-10.3.1 Arch: x86_64 (As far as I understand the *.spec-file, plugins aren't enabled in this built, so I'll have to compile my own version. Or am I wrong?) Any advice? Please let me know, if any further information is required (and please be patient, as my writing and understanding in english is limited :-)) TIA Hanns Mattes [1] http://thewalter.net/stef/software/slapi-dnsnotify/configuration.html

1 0

how to configure use of tls w/ rwm-rewritemap
by Ron Peterson 01 Jul '11

01 Jul '11

Hi, I have a rewrite map configured like: database ldap suffix "ou=myou" uri "ldap://my.backend/" tls start tls_cacertdir=/my/ca/cert/dir rwm-rewriteMap ldap uid2adminDN "ldap://my.backend/ou=yada,dc=yada?dn?sub" binddn="uid=someone,..." credentials="etc" My back end is configured to require tls, i.e. security ssf=128 update_ssf=128 simple_bind=128 If I remove that requirement, everything works. When I add it, my back end ldap server logs: Jul 1 09:24:28 mid slapd[13011]: conn=1006 op=0 BIND dn="uid=someone,..." method=128 Jul 1 09:24:28 mid slapd[13011]: conn=1006 op=0 RESULT tag=97 err=13 text=confidentiality required How do I configure rwm-rewritemap to use tls? -Ron-

2 3

stange log
by Friedrich Locke 01 Jul '11

01 Jul '11

I am seeing the log messages below on my openldap installation: @(#) $OpenLDAP: slapd 2.4.23 (Jun 28 2011 17:55:44) $ @gustav.cpd.ufv.br:/usr/ports/pobj/openldap-2.4.23/build-amd64/servers/slapd Backend ACL: access to dn.subtree="cn=monitor" by dn.base="cn=oldap,dc=ufv,dc=br" read by * none Backend ACL: access to * by * none config_back_db_open: line 0: warning: cannot assess the validity of the ACL scope within backend naming context slapd starting What does it mean? How may i avoid these messages ? What do i need to fix ? Thanks once more.

2 1

schema
by Friedrich Locke 01 Jul '11

01 Jul '11

Hi! Does anybody know where i could download the schema for simpleSecurityObject class ? Thanks in advance.

2 1

Re: schema
by ian logan 01 Jul '11

01 Jul '11

It comes with OpenLDAP, its in the Cosine schema file. On Jul 1, 2011, at 8:18 AM, Friedrich Locke wrote: > Hi! > > Does anybody know where i could download the schema for > simpleSecurityObject class ? > > Thanks in advance. >

1 0

Re: simple binds
by Friedrich Locke 01 Jul '11

01 Jul '11

Quanah, thank you for your support and patience too; now i got it working as i wished. If you come to brasil, let me know and i'll pay you some beers. Fried. On Thu, Jun 30, 2011 at 7:38 PM, Quanah Gibson-Mount <quanah(a)zimbra.com> wrote: > --On Thursday, June 30, 2011 7:22 PM -0300 Friedrich Locke > <friedrich.locke(a)gmail.com> wrote: > >> Is it possible to perform simple binds but looking up the entry's >> password in a kerberos server? > > Please spend some time reading the OpenLDAP documentation. Your question > here is clearly answered in the OpenLDAP Admin guide, section 14.5: > > <http://www.openldap.org/doc/admin24/security.html> > > --Quanah > > > -- > > Quanah Gibson-Mount > Sr. Member of Technical Staff > Zimbra, Inc > A Division of VMware, Inc. > -------------------- > Zimbra :: the leader in open source messaging and collaboration >

1 0

cn=config completely replacing slapd.conf
by David N. Blank-Edelman 01 Jul '11

01 Jul '11

(taking this to a new thread) Sorry for such a vague question, but my (perhaps failing) memory is once upon a time there were still certain backends or overlays that couldn't yet be configured via cn=config and had to be specified in slapd.conf. Has 2.4 has already cleared up all of those legacy configuration requirements or is that a 2.5 goal? Thanks! -- dNb

5 5

How to configure OpenLdap Client to work with Windows Active Directory
by yen nguyen 30 Jun '11

30 Jun '11

Hi, Can ldapsearch work with Windows AD via GSSAPI? Is there any special setting/software I need to do on the client side? On my Client system, I have Windows openldap client tools (ldapsearch ....etc). My Server system has Windows AD running. I was able to use Simple Authentication and it worked. ldapsearch.exe -H ldap://MPSD-EB01T3/ -b "dc=test,dc=com" -x I know Windows 2008 AD support GSSAPI. ldapsearch -H ldap://MPSD-EB01T3/ -xLLL -s base -b "" supportedSASLMechanisms dn: supportedSASLMechanisms: GSSAPI supportedSASLMechanisms: GSS-SPNEGO supportedSASLMechanisms: EXTERNAL supportedSASLMechanisms: DIGEST-MD5 Now I tried to use GSSAPI and it failed. Is there anything special setting I need to do on the client side to make it work? ldapsearch -H ldap://MPSD-EB01T3/ -b "cn=user1,dc=test,dc=com" -W -U user1 -Y GSSAPI -d 3 ldap_url_parse_ext(ldap://MPSD-EB01T3/) ldap_create ldap_url_parse_ext(ldap://MPSD-EB01T3:389/??base) ldap_sasl_interactive_bind_s: user selected: GSSAPI ldap_int_sasl_bind: GSSAPI ldap_new_connection 1 1 0 ldap_int_open_connection ldap_connect_to_host: TCP MPSD-EB01T3:389 ldap_new_socket: 392 ldap_prepare_socket: 392 ldap_connect_to_host: Trying 192.168.1.30:389 ldap_pvt_connect: fd: 392 tm: -1 async: 0 ldap_int_sasl_open: host=MPSD-EB01T3 ldap_err2string ldap_sasl_interactive_bind_s: Unknown authentication method (-6) additional info: SASL(-4): no mechanism available: Unable to find a calback: 2

3 3

simple binds
by Friedrich Locke 30 Jun '11

30 Jun '11

Is it possible to perform simple binds but looking up the entry's password in a kerberos server? Thanks in advance.

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

openldap-technical