Am 06.08.2012 03:57, schrieb Kurt Zeilenga:
On Aug 5, 2012, at 1:58 PM, Dora Paula dee...@gmx.net
mailto:dee...@gmx.net wrote:
Another (at least to me much better) solution seems to be to get rid
of the implicit by * none code:
So your argument that implicit rules are bad would equally
As others already said, ongoing development in an Open Source project is
a good thing.
OpenLDAP has been LDAP core standard compliant from the beginning of the
project, since it was the Open Source reference implementation.
But there are additions to the standard (see e.g. the RFC list at the
Hi Experts,
I have just started working on openldap and configured my openldap with MDB.
I am not able to locate the MDB configuration and admin guide which talks
about administration of openldap with mdb.
I am not clear about the configuration or changes i need to do to change my
release from
I have a requirement to support personalization. I didn't find many articles
to do that. Please point me some of the articles related to it.
HI,
Please explain more.
Thanks.
--
Kind Regards,
Gavin Henry.
Managing Director.
T +44 (0) 1224 279484
M +44 (0) 7930 323266
F +44 (0) 1224 824887
Hi Experts,
I have just started working on openldap and configured my openldap with MDB.
I am not able to locate the MDB configuration and admin guide which talks
about administration of openldap with mdb.
I am not clear about the configuration or changes i need to do to change my
release
Hello list.
I'm trying to provide a virtual view of the user branch in my legacy
ldap directory. Basically, the real branch uses 'localLogin' as login
attribute, and not 'uid', as usual, which unfortunatly breaks hard-coded
rules in some applications.
This configuration creates a virtual
