feat(security): Update docs for new proxy implementation#981
feat(security): Update docs for new proxy implementation#981bnevis-i merged 6 commits intoedgexfoundry:mainfrom bnevis-i:proxy-switch
Conversation
Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
| * `apps.secrets-config.proxy.tls.cert` | ||
| * `apps.secrets-config.proxy.tls.key` |
There was a problem hiding this comment.
I don't know how to code support for the pre-seeded cert. I am pretty sure this is broken.
There was a problem hiding this comment.
There is wrapper around secrets-config which is implemented here. It takes the snap options set by the user (cert and key payloads), writes them to a file, and calls secret-config internally. I have it in my to do list to move it to the edgex-go repo.
Yes it is broken. However, there is no way to make it work because secrets-config doesn't work right now in the snap because of the file ownership change: #981 (comment)
Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
| In non-secure mode of EdgeX, the API gateway is not started. | ||
|
|
||
|
|
||
| ### Local Service-to-Service - Using EdgeX Service Clients |
There was a problem hiding this comment.
I am looking for a section that explains how to hit one of the services externally on the local system. i.e. using curl or Postman. In V2 we could do this w/o a token. No in 3.0 we can not.
vyshali-chitikeshi
left a comment
There was a problem hiding this comment.
Looks good to me from validation perspective
|
This section "Prior to EdgeX 3.0, requests that originated remotely were authenticated at the API gateway via an HTTP Authorization header that contained a JWT bearer token. Internally-originated requests required no authentication. In EdgeX 3.0, the Authorization header is additionally checked at the microservice level on a per-route basis, where the majority of URL paths require authentication." it would be helpful to add details how user can add this token as authorization header with curl command or postman collection while executing rest-api's |
Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
See this commit: 072b306 |
|
LGTM |
Signed-off-by: Bryon Nevis <bryon.nevis@intel.com>
Signed-off-by: edgex-jenkins <collab-it+edgex@linuxfoundation.org>
PR Checklist
Please check if your PR fulfills the following requirements: