grpc
/
grpc-go
mirror of https://github.com/grpc/grpc-go.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

testdata: Wrap lines to 80 columns in markdown file (#8235)

This commit is contained in:
Arjan Singh Bal 2025-04-08 14:32:55 +05:30 committed by GitHub
parent be25d96c52
commit 09dd4ba0fb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
testdata/spiffe_end2end/README.md vendored
View File

@ -3,17 +3,17 @@ and `client_spiffebundle.json` are generated with the `generate.sh` and
`generate_intermediate.sh` script in this directory.
These comprise a root trust certificate authority (CA) that signs two
certificates - `client_spiffe.pem` and `server_spiffe.pem`. These are valid SPIFFE
certificates (via the configuration in `spiffe-openssl.cnf`), and the
certificates - `client_spiffe.pem` and `server_spiffe.pem`. These are valid
SPIFFE certificates (via the configuration in `spiffe-openssl.cnf`), and the
`*_spiffebundle.json` files are SPIFFE Bundle Maps for the client and server
respectively.
The SPIFFE trust bundle map files (`*_spiffebundle.json`) are manually created for
end to end testing. The `server_spiffebundle.json` contains the `foo.bar.com`
trust domain (only this entry is used in e2e tests) matching URI SAN of
`client_spiffe.pem`, and the CA certificate is `ca.pem`. The client
`spiffebundle.json` file contains `example.com` trust domain matching the URI SAN
of `server_spiffe.pem`, and the CA certificate there is also `ca.pem`.
The SPIFFE trust bundle map files (`*_spiffebundle.json`) are manually created
for end to end testing. The `server_spiffebundle.json` contains the
`foo.bar.com` trust domain (only this entry is used in e2e tests) matching URI
SAN of `client_spiffe.pem`, and the CA certificate is `ca.pem`. The client
`spiffebundle.json` file contains `example.com` trust domain matching the URI
SAN of `server_spiffe.pem`, and the CA certificate there is also `ca.pem`.
`leaf_and_intermediate_chain.pem` is a certificate chain whose leaf is a valid
SPIFFE cert that is signed by an intermediate CA (`intermediate_ca.pem`). The