--On Thursday, October 26, 2023 8:07 AM + "Frank, Michael"
wrote:
Can someone state why this mission is hopeless in detail or should the
setup work basically ?
I would suspect the replication DN doesn't have full read access to the
object, but fairly difficult to know w/o more informati
--On Tuesday, October 24, 2023 10:01 AM +0200 Óscar Remírez de Ganuza
Satrústegui wrote:
What architecture would you suggest for implementing lastbind?
Is it better to use a Master-Slave with the chain overlay to send the
lastbind writes from the slave to the master?
If you want the valu
--On Thu> Try the following (and replace with the correct URL):
$ ldifmodify -x -H ldap://localhost/ -D cn=config -W << EOF
> dn: olcDatabase={0}config,cn=config
> changetype: modify
> add: olcRootPW
> olcRootPW: {SSHA}cZbRoOhRew8MBiWGSEOiFX0XqbAQwXUr
> EOF
There doesn't appear to be a
Hi,
when comparing the LDIF you used to initialize with the slapcat output, what I can see is that you have no distict
definition of olcDatabase={0}config,cn=config. I suspect that OpenLDAP then used default vaules, including the "to * by
* none" ACL.
How mission critical is this server? Can
Airbus Amber
Dear all,
basically I trying to establish a syncrepl/refreshAndpersist Setup between:
OpenLDAP: 2.4.57.0.1 @ Solaris < - > OpenLDAP: 2.6.2-3 @ Rhel 9.latest
(don`t ask)
An intial syncrepl activation does works properly (replication of ou`s content
in both directions), but when I aft
OpenLDAP 2.6.6r1 on Apline Linux aarch64
Not sure what I am doing wrong but I am unable to change the
rootDN's password.
# ldapmodify -H ldapi:/// -Y EXTERNAL -D 'cn=config' << EOF
> dn: olcDatabase={0}config,cn=config
> changetype: modify
> add: olcRootPW
> olcRootPW: {SSHA}cZbRoOhRew8MBiWGSEOiF
