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

Migrate ssl truststore into a secret (Jupyter) #176

Open
planetf1 opened this issue Aug 15, 2022 · 0 comments
Open

Migrate ssl truststore into a secret (Jupyter) #176

planetf1 opened this issue Aug 15, 2022 · 0 comments

Comments

@planetf1
Copy link
Member

planetf1 commented Aug 15, 2022

Currently the truststore - ie the certificate chain relating the servers we trust (Egeria's root & intermediate Cases, which sign the server cert used by the server chassis) is stored in a configmap.

Generally, certificates, passwords etc should be stored in secrets as these are more secure and opaque.

In this case the exposure is negligible given

  • this is only for demo purposes
  • previously we didn't validate certs
  • this is only an additional root certificate -- these are often provided clear text anyway when installed on an O/S
  • these are only our self-signed cert chain
@planetf1 planetf1 changed the title Migrate ssl truststore into a secret Migrate ssl truststore into a secret (Jupyter) Aug 15, 2022
@planetf1 planetf1 transferred this issue from odpi/egeria-coco-labs Aug 15, 2022
@planetf1 planetf1 self-assigned this Aug 25, 2022
@planetf1 planetf1 moved this to Security in Egeria V4.0 Planning Dec 5, 2022
@planetf1 planetf1 moved this to Todo in Egeria V4.0 Planning Dec 5, 2022
@planetf1 planetf1 removed their assignment Jun 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
No open projects
Status: Todo
Development

No branches or pull requests

1 participant