OpenLdap 写入时重定向
我目前正在尝试为 OpenLdap 2.2 的安装设置写入重定向。
我有两个实例正在运行。其中一个配置为只读（仅读取访问权限，数据库指定为只读），并将重定向配置为指向第二个实例。第二个实例配置为允许所需的写入权限。
当我尝试对第一个实例进行修改时，它按预期失败，但没有发回引用。我是否缺少某个配置？我是否走在正确的道路上？任何指导将不胜感激。谢谢。
I am currently trying to setup a redirect on write for an installation of OpenLdap 2.2.
I have two instances running. One is configured to be read-only (only read access, database specified as read-only) and has redirect configured to point to the second instance. The second instance is configured to allow for the desired write permissions.
When I attempt a modify on the first instance it fails as expected but does not send back the referral. Am I missing a piece of the configuration? Am I even on the right path? Any guidance would be greatly appreciated. Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
在
slapd.conf的数据库部分中，您是否添加了这样的重定向？ :In the database section of you
slapd.confdo you add the redirection like this ? :因此，事实证明，执行此操作的最佳方法是继续使用 slurpd 设置复制并将所有请求指向从属实例。不幸的是，您无法在同一主机上设置主服务器和从服务器（出于明显的原因，但仍然如此），因此我必须启动第二个虚拟机才能实现这一点。
老实说，如果我不想复制重定向问题，那是不值得的，但我必须复制生产问题。
有关 slapd 特别是 slurpd 的更多信息，OpenLDAP 文档实际上非常有用：slurpd config for OpenLDAP 2.2
So, it turns out the best way to do this is to go ahead and set up replication using slurpd and point all requests at the slave instance. Unfortunately you can't set up the master and slave on the same host (for obvious reasons, but still), so I had to spin up a second VM to get this going.
Honestly, if I was not trying to replicate a redirect problem it wouldn't be worth it, but I have to duplicate a production issue.
For more information on slapd and specifically slurpd, the OpenLDAP documentation is actually crazy helpful: slurpd config for OpenLDAP 2.2