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
If LDAP_BINDPASS contains a special character (like $ or #) , when an error at start "bad substitution...." , and SSP is not able to connect to ldap server beacause LDAP_BINDPASS is set to default value in file config.inc.php
Steps to reproduce
Start containers with an LDAP_BINDPASS containing special characters: P@s$word
What is the expected correct behavior?
Not error at start and SSP work
Possible fixes
it's due to sed command in install/assets/functions/30-self-service-password
The text was updated successfully, but these errors were encountered:
rpo-fr
changed the title
Error at start with ldap_passwd with special characters
Error at start with LDAP_BINDPASS with special characters
Jan 19, 2023
$ should be able to work provided you prefix it with $$ however you are right about #. That is what I use for separating the sed statements aka sed s#bind_pass=blank#bind_pass=$LDAP_BIND_PASS#g". Would probably have to find a very esoteric seperator, but even till whomever had that would probably still face the issue. If you have any other ideas on how to get that in there I am all ears.
Summary
If LDAP_BINDPASS contains a special character (like $ or #) , when an error at start "bad substitution...." , and SSP is not able to connect to ldap server beacause LDAP_BINDPASS is set to default value in file config.inc.php
Steps to reproduce
Start containers with an LDAP_BINDPASS containing special characters: P@s$word
What is the expected correct behavior?
Not error at start and SSP work
Possible fixes
it's due to sed command in install/assets/functions/30-self-service-password
The text was updated successfully, but these errors were encountered: