Hi,
A big thanks to you and all others who replied to my original question.
Sorry for my belated reply, as I was experimenting with various options
as per your suggestions.
Anyway, in the end the simplest way to achieve what I wanted was to stop
the existing Slapd daemon, remove the old database
Jon Smark writes:
> Hi,
>
> I'm new to OpenLDAP and I'm finding it hard to perform the initial
> configuration (a lot of the information I find online seems to
> pertain only to old versions of OpenLDAP, which used a different
> configuration system).
>
> Anyway, I have
On Fri, 14 Jul 2017, Jon Smark wrote:
> I'm new to OpenLDAP and I'm finding it hard to perform the initial
> configuration (a lot of the information I find online seems to pertain
> only to old versions of OpenLDAP, which used a different configuration
> system).
Did you try the documentation
John Lewis wrote:
> I only found two caveats, it doesn't mask password well and it shows
> how many characters your password is instead of nothing like it should
> in my opinion.
Indeed that is room for improvement. But it does not really matters if
you authenticate using
On Fri, 2017-07-14 at 14:48 +, Jon Smark wrote:
> Hi,
>
>
>
> I'm new to OpenLDAP and I'm finding it hard to perform the initial
>
> configuration (a lot of the information I find online seems to
> pertain only to old versions of OpenLDAP, which used a different
>
> configuration
On Fri, Jul 14, 2017 at 02:48:30PM +, Jon Smark wrote:
Anyway, I have defined a schema file with the custom attributes
and object classes relevant to my domain. Starting from a fresh
installation of OpenLDAP 2.4.42 running on Ubuntu 16.04, I want
to configure my Slapd server to *only*
Hi,
I'm new to OpenLDAP and I'm finding it hard to perform the initial
configuration (a lot of the information I find online seems to
pertain only to old versions of OpenLDAP, which used a different
configuration system).
Anyway, I have defined a schema file with the custom attributes
and