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.

Sign up for GitHub

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

Jump to bottom

Secure Kong admin port with TLS #1941

Closed
bnevis-i opened this issue Oct 16, 2019 · 0 comments · Fixed by edgexfoundry/edgex-docs#287
Closed

Secure Kong admin port with TLS #1941

bnevis-i opened this issue Oct 16, 2019 · 0 comments · Fixed by edgexfoundry/edgex-docs#287
Labels
enhancement New feature or request security-services wontfix This will not be worked on

Comments

@bnevis-i
Copy link
Collaborator

bnevis-i commented Oct 16, 2019 •
edited
Loading

🚀 Feature Request

Relevant Package

Affects security-secrets-setup (PKI) and Kong configuration

Description

The Kong admin port is used to configure the proxy and this port handles sensitive data, for example, the TLS private key for the external-facing traffic port. Currently GetProxyBaseURL generates a URL to do this sensitive configuration over unprotected HTTP. CWE-319

Describe the solution you'd like

  • Modify security-secret-setup to generate a TLS certificate for the kong admin port (using the internal hostname as the subject CN).
  • Pass the generated certificate via the file system
  • Docker: Configure the environment variables KONG_ADMIN_SSL, KONG_ADMIN_SSL_CERT, and KONG_ADMIN_SSL_KEY to use the certificate.
  • Snaps: Use the similarly-named configuration file directives. (See kong config reference)
  • Modify security-proxy-setup to configure over TLS
  • Kong startup should block until the required TLS assets are available on the file system.

Related issues
@bnevis-i bnevis-i added enhancement New feature or request security-services labels Oct 16, 2019
@tingyuz tingyuz added the geneva label Oct 18, 2019
@brandonforster brandonforster added this to the EdgeX Geneva milestone Oct 25, 2019
@bnevis-i bnevis-i added the unscoped Issues that are currently out of scope for all releases. label Nov 20, 2019
@bnevis-i bnevis-i removed this from the EdgeX Geneva milestone Nov 20, 2019
@brandonforster brandonforster added this to the EdgeX Geneva milestone Nov 22, 2019
@bnevis-i bnevis-i removed the geneva label Dec 4, 2019
@bnevis-i bnevis-i removed this from the EdgeX Geneva milestone Dec 4, 2019
@bnevis-i bnevis-i mentioned this issue Nov 4, 2020
Closed
@bnevis-i bnevis-i mentioned this issue Nov 18, 2020
Merged
4 tasks
@bnevis-i bnevis-i added wontfix This will not be worked on and removed unscoped Issues that are currently out of scope for all releases. labels Nov 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request security-services wontfix This will not be worked on
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

feat(adr): ADR for detailing when TLS is or is not used
3 participants
@brandonforster @bnevis-i @tingyuz