Skip to content
This repository was archived by the owner on Aug 7, 2020. It is now read-only.

can not set auth.http.auth_req.params with docker environments #21

Closed
CrazyPandar opened this issue Sep 5, 2017 · 3 comments
Closed
Assignees
Milestone

Comments

@CrazyPandar
Copy link

run EMQ by docker with following command:

docker run --rm -ti --name emq -p 192.168.128.30:18083:18083 -p 8883:8883 -p 8084:8084 \
-e EMQ_NODE__PROCESS_LIMIT=2097152 \
-e EMQ_NODE__MAX_PORTS=1048576 \
-e EMQ_MQTT__ALLOW_ANONYMOUS=false \
-e EMQ_MQTT__CACHE_ACL=false \
-e EMQ_MQTT__MQUEUE__MAX_LENGTH=8 \
-e EMQ_LISTENER__TCP__EXTERNAL__ACCEPTORS=64 \
-e EMQ_LISTENER__TCP__EXTERNAL__MAX_CLIENTS=1024000 \
-e EMQ_LISTENER__SSL__EXTERNAL__MAX_CLIENTS=1024000 \
-e EMQ_LISTENER__WS__EXTERNAL__MAX_CLIENTS=1024000 \
-e EMQ_LISTENER__WSS__EXTERNAL__MAX_CLIENTS=1024000 \
-e EMQ_SYSMON__LARGE_HEAP=64MB \
-e EMQ_LOADED_PLUGINS="emq_recon,emq_modules,emq_retainer,emq_dashboard,emq_auth_http" \
-e EMQ_AUTH__HTTP__AUTH_REQ="http:\/\/192.168.128.30:12101\/mqtt\/auth" \
-e EMQ_AUTH__HTTP__AUTH_REQ__PARAMS="clientid=%c,username=%u,password=%P,ipaddr=%a" \
-e EMQ_AUTH__HTTP__SUPER_REQ="http:\/\/192.168.128.30:12101\/mqtt\/superuser" \
-e EMQ_AUTH__HTTP__ACL_REQ="http:\/\/192.168.128.30:12101\/mqtt\/acl" \
emq:2.2

alll evnironments take effect within docker except auth.http.auth_req.params failed to be set.

@emqplus emqplus added this to the 2.3-beta.4 milestone Sep 5, 2017
@turtleDeng
Copy link

turtleDeng commented Oct 9, 2017

@CrazyPandar

EMQ_AUTH__HTTP__AUTH_REQ="http:\\/\\/192.168.128.30:12101\\/mqtt\\/auth"

@AutomationD
Copy link

AutomationD commented Mar 20, 2018

Why are we closing this? IMO we should rather do sanitation instead of forcing people to escape forward slashes. Why not just do another sed -e 's/\//\\\//'?

@gyuuu
Copy link

gyuuu commented Sep 21, 2018

At least indicate somewhere that /-s has to be escaped with \/, I spent more than 2 hours finding it out, discussions in github tickets indicate different escape sequences, no other documentation is available or I was nat able to find it.

Please include the actual escape sequence in the documentation. If someone can comfirm that this is the right sequence and it's not working because of some kind of bug, I can submit a pull request updating the documentation.

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

No branches or pull requests

5 participants