Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error at start with LDAP_BINDPASS with special characters #63

Open
rpo-fr opened this issue Jan 19, 2023 · 1 comment
Open

Error at start with LDAP_BINDPASS with special characters #63

rpo-fr opened this issue Jan 19, 2023 · 1 comment
Labels

Comments

@rpo-fr
Copy link

rpo-fr commented Jan 19, 2023

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

@rpo-fr rpo-fr added the bug label Jan 19, 2023
@rpo-fr 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
@tiredofit
Copy link
Owner

$ 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants