Any idea where we should look? I can go huntin'.
On 12/12/18, 5:40 PM, "Phil Sorber" wrote:
FWIW, I made a tool that handled this all. You could pass it a bundle and
it would create a minimal chain to install. Would be great if someone could
find that code and open source it. It wa
FWIW, I made a tool that handled this all. You could pass it a bundle and
it would create a minimal chain to install. Would be great if someone could
find that code and open source it. It was written in Go and could likely be
integrated into the UI.
Thanks.
On Wed, Dec 12, 2018 at 4:27 PM Gray, J
Something to think about, intermediate cert chains are ordered and of
indeterminate length if present at all. Also, for a given root CA, there may
be multiple variants of intermediate cert chains.
Jonathan G
On 12/12/18, 9:50 AM, "Howell, Jeff (Contractor)"
wrote:
Greetings Traffic Con
Greetings Traffic Controllers.
I have an idea for a change in how SSL certs are managed in TO/TP. Currently we
have to concatenate the intermediate certs onto the server cert and paste that
into the SSL key interface. As the intermediate is likely the same for the
majority of certs in the cdn,
Imagine the following tenant tree:
- root
-- tenant A (2 users, 4 delivery services)
--- tenant A.A (5 users, 3 delivery services)
-- bad tenant B (6 users, 2 delivery services)
--- bad tenant B.B (3 users, 4 delivery services)
Because tenant B is misbehaving, you can currently do this manually:
RE: disabling the root tenant being impossible: I'm not sure that there's a
specific check for that, it's just that one cannot submit a `PUT` request for
it because it cannot be assigned to one of its own children, and the endpoint
won't allow a `null` or `undefined` "parentId". A future `PATCH`
