Andy wrote:
Currently I have a ldap directory with several branches.
--Root
ou=Samba accounts
ou=Website accounts
ou=VPN accounts
ou=Email accounts
and so on.
Every object has a userPassword field which means that if a user changes
his password under one of the systems (eg.
Hello,
in the mailing list's archive is a lot of stuff about OpenLDAP as proxy
for another LDAP-Server using the ldap/meta backend, but I didn't find an
answere of my question (it's possible that I don't see the wood for the
trees).
I've the following problem:
Our OpenLDAP get's an request
Le jeudi 08 mai 2008 à 01:08 +0200, Pierangelo Masarati a écrit :
Raphaël 'SurcouF' Bordet wrote:
You've probably misunderstood my request.
An example will be more efficient :
I've some entries like this:
dn: uid=raphael.bordet,dc=xxx,dc=yy
objectclass: top
objectclass:
I don't recommend using the official redhat packages for running a
server (some versions have been known to be problematic). If I
recall, RedHat includes them more for compatibility and dependency
rather than running as a server.
With that said, try running your slapd with debug to see
The Hwyman wrote:
I'm running Red Hat Enterprise 5 (x86_64) and Openldap version 2.3.27
from official rpms. I have installed openldap, openldap-devel,
openldap-clients, and openldap-servers.
The following command:
ldapsearch -x -b dc=example,dc=com '(uid=jsmith)'
produces the following
[EMAIL PROTECTED] wrote:
I need as a response of a request an interaction of two LDAP-Server.
From the other LDAP-Server the authentification and if successfull from
our LDAP-Server the attributes.
Is there a fair chance to get a solution using the ldap/meta backend.
Just a hint without
Raphaël 'SurcouF' Bordet wrote:
Thanks for this tips, it's works fine.
databaserelay
suffix o=Example,c=US
relay dc=example,dc=com
overlay rwm
rwm-rewriteEngine on
rwm-rewriteMap ldap mail2uid
Pierangelo Masarati [EMAIL PROTECTED] wrote:
Only DN-valued attributes. It (intentionally) doesn't work for other
attrs.
Why? I recently atempted to use it and gave up because of that.
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
[EMAIL PROTECTED]
Hello all,
I'm not quite sure if my mind plays a trick on me, but was there a way
to save eg. (for readability I'll use HTML-Entities, of course it should
and will be UTF-8 in LDIF)
dn: ...
cn: Muuml;ller
and find it with the filter
(cn=Mueller)
?
Or do I have to save all permutations of
I'm looking for a way to prevent a specific DN from a remote server
from showing up when being accessed through back-ldap (specifically,
slapo-translucent).
I have tried something like this:
access to dn.base=cn=psu.facstaff,dc=psu,dc=edu
by * none
This actually ended up preventing other
Hi!
Here
http://www.openldap.org/lists/openldap-software/200701/msg00315.html
I read:
In general, the syncrepl provider in OpenLDAP 2.2 is not safe for use.
What does save refer to:
- It can easily be hacked?
- It can easily crash the master server?
- It might be that not everything gets
Christian Marg writes:
I'm not quite sure if my mind plays a trick on me, but was there a way
to save eg. (for readability I'll use HTML-Entities, of course it should
and will be UTF-8 in LDIF)
dn: ...
cn: Muuml;ller
and find it with the filter
(cn=Mueller)
?
None that I remeber.
Or do
Andrew Cobaugh writes:
I have tried something like this:
access to dn.base=cn=psu.facstaff,dc=psu,dc=edu
by * none
This actually ended up preventing other dn's from showing up.
Prevented others from showing up in what kind of searches? It also
prevents you from using that DN as the base
Emmanuel Dreyfus wrote:
Pierangelo Masarati [EMAIL PROTECTED] wrote:
Only DN-valued attributes. It (intentionally) doesn't work for other
attrs.
Why? I recently atempted to use it and gave up because of that.
Because the purpose of slapo-rwm is to muck with naming contexts to
implement
Pierangelo Masarati [EMAIL PROTECTED] wrote:
Because the purpose of slapo-rwm is to muck with naming contexts to
implement virtual views on data. Arbitrary access to attribute values
means mucking with users' data, which is considered a bad practice. In
any case, feel free to remove that
Hello Christian,
maybe you could use slapo_rwm to rewrite Mueller to Müller. The rewrite
rule could look like this (very much like the add/eat blanks examples):
rwm-rewriteRule(.*)ae(.*) $1ä$2
The same should be possible for ö ü and ß. I'm not shure if this will
work, as it is an idea,
16 matches
Mail list logo
