-
Notifications
You must be signed in to change notification settings - Fork 7
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
feat: add certificates for ssl test and an ssl test image #168
feat: add certificates for ssl test and an ssl test image #168
Conversation
links to #159 |
tested with java, worked |
Signed-off-by: Simon Schrottner <[email protected]>
01ee717
to
742ad5f
Compare
the only thing which we might want to add, is also a gherkin file for testing, but on the other hand, we could reuse the evaluation.feature with the basic testing flags |
@@ -0,0 +1,52 @@ | |||
-----BEGIN PRIVATE KEY----- |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we make this a GitHub secret? I know it's just for testing but I'm afraid scanners might pick this up and open issues in the repo.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well we could theoretically - I would for now leave it as is, and optimize if needed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ya I would rather just ignore it in whatever tools flag it.
👏 👏 👏 👏 Can't wait to have this implemented in various places. I'd be happy to help. |
This adds another image protected via an SSL certificate with a custom CA.
If a key is used, the password is
flagd
in the creation process.dockerfile improvements
Instead of having now two different dockerfiles, copying the files, and executing the script, i reduced one layer, by depending on the testbed image and only changing the entry point
testing
first run the docker container
docker run --rm -p 8013:8013 flagd-testbed-ssl
curl -v --cacert ./custom-root-cert.crt https://localhost:8013/health
should run in to 404curl -v https://localhost:8013/health
should run in to a cert errorcloses #159