cc889443a5
connect: don't colon-hex-encode the AuthorityKeyId and SubjectKeyId fields in connect certs ( #6492 )
...
The fields in the certs are meant to hold the original binary
representation of this data, not some ascii-encoded version.
The only time we should be colon-hex-encoding fields is for display
purposes or marshaling through non-TLS mediums (like RPC).
2019-09-23 12:52:35 -05:00
ce29660245
website: update docs for leaf cert TTL option
2018-07-16 13:33:42 -07:00
d3cec142d4
website: fix an assortment of broken links
2018-06-25 12:26:24 -07:00
6dfc0d848b
website: correct a few last things in CA docs
2018-06-25 12:26:23 -07:00
99562a0153
website: split out CA docs by provider type
2018-06-25 12:26:23 -07:00
6ad5476f1b
website: fix example config in vault CA docs
2018-06-25 12:26:09 -07:00
fcc5dc6110
connect/ca: leave blank root key/cert out of the default config (unnecessary)
2018-06-25 12:25:42 -07:00
76aa137ffc
website: add Vault CA provider doc sections
2018-06-25 12:25:42 -07:00
86200f2d03
docs: add Connect CA overview
2018-06-25 12:25:10 -07:00
8dbe0017bb
Starting Docs ( #46 )
...
* website: first stab at Connect docs
* website: lots more various stuff (bad commit messages)
* website: getting started page for Connect
* website: intentions
* website: intention APIs
* website: agent API docs
* website: document agent/catalog proxy kind service values
* website: /v1/catalog/connect/:service
* website: intention CLI docs
* website: custom proxy docs
* website: remove dedicated getting started guide
* website: add docs for CA API endpoints
* website: add docs for connect ca commands
* website: add proxy CLI docs
* website: clean up proxy command, add dev docs
* website: todo pages
* website: connect security
2018-06-25 12:24:05 -07:00
R.B. Boyer