consul

Commit Graph

Author	SHA1	Message	Date
freddygv	fac3ddc857	Use internal server certificate for peering TLS 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.	2022-10-07 09:05:32 -06:00
DanStough	2a2debee64	feat(peering): validate server name conflicts on establish	2022-09-14 11:37:30 -04:00
DanStough	e617e7df3e	feat(cli): add initial peering cli commands	2022-09-01 17:20:13 -04:00

Author

SHA1

Message

Date

freddygv

fac3ddc857

Use internal server certificate for peering TLS

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.

2022-10-07 09:05:32 -06:00

DanStough

2a2debee64

feat(peering): validate server name conflicts on establish

2022-09-14 11:37:30 -04:00

DanStough

e617e7df3e

feat(cli): add initial peering cli commands

2022-09-01 17:20:13 -04:00

3 Commits (693c8a4706e10bc8cd212ceaf0b6728045e96e17)