You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I plan to migrate from the unsupported Osixia OpenLDAP image to the bitnami.
After some tests, I see that my application fails when using the post-read control.
The main clue in the OpenLDAP log is get_ctrls failed
What is the feature you are proposing to solve the problem?
I would suggest to enable the post-read control if possible.
Honestly, I am not even sure how to do this. The control had always been enabled by default on OpenLDAP instances I interacted with, and it appears to not be very documented.
Thank you for the feature request! We would need to know if this is something that is enabled at openldap compilation or this is an external extension that must be installed. Let's see if someone from the community can share their knowledge, if not we will check it ourselves but we cannot guarantee an ETA as it is not a critical feature.
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback.
Name and Version
bitnami/openldap 2.6.9
What is the problem this feature will solve?
I plan to migrate from the unsupported Osixia OpenLDAP image to the bitnami.
After some tests, I see that my application fails when using the post-read control.
The main clue in the OpenLDAP log is
get_ctrls failed
What is the feature you are proposing to solve the problem?
I would suggest to enable the post-read control if possible.
Honestly, I am not even sure how to do this. The control had always been enabled by default on OpenLDAP instances I interacted with, and it appears to not be very documented.
The control is described in RFC4527.
The OpenLDAP doc indicates that the extension is supported: https://www.openldap.org/faq/data/cache/645.html
Sorry for the noise due to my double ticket #76838
The text was updated successfully, but these errors were encountered: