From cfb5f66ed5755fb0bf9929432f9223094f395dea Mon Sep 17 00:00:00 2001 From: Bryon Nevis Date: Wed, 5 Jan 2022 07:29:16 -0800 Subject: [PATCH] fix: Pass Kong admin JWT to secrets-config utility (#664) Fixes #651 Signed-off-by: Bryon Nevis --- docs_src/security/Ch-APIGateway.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs_src/security/Ch-APIGateway.md b/docs_src/security/Ch-APIGateway.md index 1621c0a5a6..8324f246a4 100644 --- a/docs_src/security/Ch-APIGateway.md +++ b/docs_src/security/Ch-APIGateway.md @@ -84,7 +84,7 @@ SNI at all. Run the following command to install a custom certficate using the assumptions above: - docker-compose -p edgex -f docker-compose.yml run --rm -v `pwd`:/host:ro --entrypoint /edgex/secrets-config edgex-proxy proxy tls --incert /host/cert.pem --inkey /host/key.pem --snis edge001.example.com + docker-compose -p edgex -f docker-compose.yml run --rm -v `pwd`:/host:ro --entrypoint /edgex/secrets-config edgex-proxy proxy tls --incert /host/cert.pem --inkey /host/key.pem --snis edge001.example.com --admin_api_jwt /tmp/edgex/secrets/security-proxy-setup/kong-admin-jwt The utility will always add the internal host names, "localhost" and "kong" to the specified SNI list.