https://bugs.openldap.org/show_bug.cgi?id=7372
--- Comment #2 from Nadezhda Ivanova <nivanova(a)symas.com> ---
I wasn't able to reproduce this issue in 2.5 - failover worked for me both with
-j DROP and when back-end ldap service was stopped.
Based on the described behavior, there was some issue during initial bind of a
connection that was fixed in the 9 since then, or it was a misconfiguration.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9610
Issue ID: 9610
Summary: Missing config.h
Product: OpenLDAP
Version: 2.5.5
Hardware: x86_64
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: build
Assignee: bugs(a)openldap.org
Reporter: jb00356987(a)techmahindra.com
Target Milestone: ---
Dears,
When I tried to compile custom overlays written in "C", I get errors vs missing
config.h file.
I noticed it was missing from openldap2.5.5/servers/slapd/ directory but I
found it in openldap2.4.59/servers/slapd/ directory.
After I copied from 2.4.59 to 2.5.5 directory, I was able to compile but I'm
not sure this is the correct version for 2.5.5 and why it's not present ?
Can you advice ?
Thx,
Jean-Luc.
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9609
Issue ID: 9609
Summary: Unrecognized database type (monitor)
Product: OpenLDAP
Version: 2.4.59
Hardware: All
OS: Linux
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: backends
Assignee: bugs(a)openldap.org
Reporter: fdepaz(a)vmware.com
Target Milestone: ---
Hello,
I'm getting issues setting up the monitor backend in OpenLDAP 2.4.59, with it
throwing the following error:
----
Unrecognized database type (monitor)
60edd056 olcDatabase: value #0: <olcDatabase> failed init (monitor)
slapadd: could not add entry dn="olcDatabase={1}monitor,cn=config" (line=631):
----
It seems it is not detecting "monitor" as a valid database backend. My monitor
configuration via cn=config is the following:
----
dn: olcDatabase=monitor,cn=config
objectClass: olcDatabaseConfig
olcDatabase: monitor
...
----
This same configuration is working without issues using both the previous
version 2.4.58 and the newest 2.5.5, but not in 2.4.59.
Regards,
Francisco de Paz
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7215
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7080
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Assignee|bugs(a)openldap.org |ondra(a)mistotebe.net
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=9211
Bug ID: 9211
Summary: Relax control is not consistently access-restricted
Product: OpenLDAP
Version: 2.4.49
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: ---
Component: slapd
Assignee: bugs(a)openldap.org
Reporter: ryan(a)openldap.org
Target Milestone: ---
The following operations can be performed by anyone having 'write' access (not
even 'manage') using the Relax control:
- modifying/replacing structural objectClass
- adding/modifying OBSOLETE attributes
Some operations are correctly restricted:
- adding/modifying NO-USER-MODIFICATION attributes marked as manageable
(Modification of non-conformant objects doesn't appear to be implemented at
all.)
In the absence of ACLs for controls, I'm of the opinion that all use of the
Relax control should require manage access. The Relax draft clearly and
repeatedly discusses its use cases in terms of directory _administrators_
temporarily relaxing constraints in order to accomplish a specific task.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.openldap.org/show_bug.cgi?id=8197
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.0 |2.7.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=7347
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.0 |2.7.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8375
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.0 |2.7.0
--
You are receiving this mail because:
You are on the CC list for the issue.
https://bugs.openldap.org/show_bug.cgi?id=8485
Quanah Gibson-Mount <quanah(a)openldap.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|2.6.0 |2.7.0
--
You are receiving this mail because:
You are on the CC list for the issue.