mirror of https://github.com/hashicorp/consul
fac3ddc857
A previous commit introduced an internally-managed server certificate to use for peering-related purposes. Now the peering token has been updated to match that behavior: - The server name matches the structure of the server cert - The CA PEMs correspond to the Connect CA Note that if Conect is disabled, and by extension the Connect CA, we fall back to the previous behavior of returning the manually configured certs and local server SNI. Several tests were updated to use the gRPC TLS port since they enable Connect by default. This means that the peering token will embed the Connect CA, and the dialer will expect a TLS listener. |
||
|---|---|---|
| .. | ||
| ca | ||
| authz.go | ||
| authz_test.go | ||
| common_names.go | ||
| csr.go | ||
| generate.go | ||
| generate_test.go | ||
| parsing.go | ||
| sni.go | ||
| sni_test.go | ||
| testing_ca.go | ||
| testing_ca_test.go | ||
| testing_spiffe.go | ||
| uri.go | ||
| uri_agent.go | ||
| uri_agent_oss.go | ||
| uri_agent_oss_test.go | ||
| uri_mesh_gateway.go | ||
| uri_mesh_gateway_oss.go | ||
| uri_mesh_gateway_oss_test.go | ||
| uri_server.go | ||
| uri_service.go | ||
| uri_service_oss.go | ||
| uri_service_oss_test.go | ||
| uri_signing.go | ||
| uri_signing_test.go | ||
| uri_test.go | ||
| x509_patch.go | ||
| x509_patch_test.go | ||