github
/
consul
mirror of https://github.com/hashicorp/consul
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
19,220 Commits
1,703 Branches
464 Tags
733 MiB
Commit Graph

4 Commits (07f0f07d5e302016a4e0fecffb1e7268c0e577be)

Author SHA1 Message Date
hc-github-team-consul-core c896ae06bf
Backport of Bring back parameter ServerExternalAddresses in GenerateToken endpoint into release/1.14.x (#15296) 
* backport of commit 4199a7c30a

* backport of commit 53be93fb90

* backport of commit 1b0ce4e96c

* backport of commit 1b4ee792cb

* backport of commit 98f3d5aa51

* backport of commit 1f3b30b768

* Fix gomod for merging.

Co-authored-by: Nitya Dhanushkodi <nitya@hashicorp.com>
Co-authored-by: Derek Menteer <derek.menteer@hashicorp.com>
 2022-11-08 15:31:17 -06:00
Nitya Dhanushkodi 5e156772f6
Remove ability to specify external addresses in GenerateToken endpoint (#14930) 
* Reverts "update generate token endpoint to take external addresses (#13844)"

This reverts commit f47319b7c6.
 2022-10-19 09:31:36 -07:00
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 e617e7df3e feat(cli): add initial peering cli commands 2022-09-01 17:20:13 -04:00