DevFW-CICD/ingress-nginx-helm
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

update docs with a warning about cert chain order (#7908)

Browse source
This commit is contained in:
James Strong 2021-11-12 14:34:29 -05:00 • committed by GitHub
parent 100057d0c5
commit 8333c8c127
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23
2 changed files with 6 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

4
docs/examples/PREREQUISITES.md
View file

@ -26,7 +26,7 @@ Note: If using CA Authentication, described below, you will need to sign the ser
CA Authentication also known as Mutual Authentication allows both the server and client to verify each others
identity via a common CA.
We have a CA Certificate which we obtain usually from a Certificate Authority and use that to sign
We have a CA Certificate which we usually obtain from a Certificate Authority and use that to sign
both our server certificate and client certificate. Then every time we want to access our backend, we must
pass the client certificate.
@ -54,6 +54,8 @@ openssl x509 -req -sha256 -days 365 -in client.csr -CA ca.crt -CAkey ca.key -set
Once this is complete you can continue to follow the instructions [here](./auth/client-certs/README.md#creating-certificate-secrets)
## Test HTTP Service
All examples that require a test HTTP Service use the standard http-svc pod,