Fix ldap related critical Problems#644
Conversation
* no more consumption about value
|
Thanks @alinmear |
|
Thanks for this, I will try it out if I get a chance later this week |
|
Thank you, I really didn't have the time to check the source to fix #591 so this mr will come in handy. |
|
The new variable don't work because they are in comment. Why is this? |
|
@johansmitsnl, these are only default values. If you want to change those values you need to set the corresponding ENV Variables, like: I already wrote an example within the readme. Update1: I commented those defaults, because I am not sure, if this could lead to some unexpected behavior in some setups, if i set user and pass filter equal. Update2: The main substitution is triggered by this call btw: |
|
Inside the docker: It seems that the variables are not applied but they are set in the ENV. |
|
@johansmitsnl , the problem here is the (&(objectClass=PostfixBookMailAccount)(\|(uniqueIdentifier=%n)(mail=%u)))This should work. I check how to deal with this kind of characters and sed, because currently we are doing the sed calls like: sed -i -e "s|somethingelse|somethingelse-new|g"Update: I found a solution by escaping the special character before the string is handed over to |
As already written by me (#641 (comment)) we have some serious issues regarding the setup of ldap with env variables.
This pr should fix the following issues: #641, #633, #491 (see comments), #636 (can be configured explicit with the new env vars; maybe we should discuss better defaults as stated there), #591
LDAP_QUERY_FILTER_USERLDAP_QUERY_FILTER_GROUPLDAP_QUERY_FILTER_ALIASDOVECOT_USER_FILTERDOVECOT_PASS_FILTERWe may should discuss some defaults and or combinations to make the setup more straight forward (like dovecot user_filter and pass_filter could be the same, when only 1 has been defined or LDAP_QUERY_FILTER_USER could be set for the saslauthd part if not explicitly set).
Hope this helps ...