Côme Chilliet wrote:
> I already extracted the EXOP part and ported it to PHP master
I see the thing has been committed, which is nice. It seems ldap_refresh
is missing, though. Was it omitted on purpose?
--
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
m...@netbsd.org
Howard Chu wrote:
> > Elliptic Curve support for OpenSSL was added in master branch 4 years
> > ago (ITS#7595). Is there any plan to backport EC support for OpenSSL in
> > 2.4 branch ?
>
> OpenLDAP 2.4 is feature-frozen. All new features are 2.5 only.
For however is interested,
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
Thank you both for the advice. I appreciate it.
It seems like indexing aliasedObjectName helped. but I also put a problem
system on its own replica. load from slapd seemed to drop from 1500% down
to a normal level, <50%.
Instead of having separate copies of each user in separate branches. We
On 14/07/17 20:57, Josh Catana wrote:
Thank you both for the advice. I appreciate it.
It seems like indexing aliasedObjectName helped. but I also put a
problem system on its own replica. load from slapd seemed to drop from
1500% down to a normal level, <50%.
Nice replica:-) I don't see how
On 13. juli 2017 16:35, Josh Catana wrote:
We heavily rely on aliases to different OUs to manage access to different
environments, prod/dev/qa/etc.
Don't. Having lots of aliases cancels out the effect of your indexes:
Looking at what it's doing it spending a lot of time with bld_idl_union in