Kenneth Jenkins 3ebee1159c add downstream mTLS integration test cases (#4234) ... * integration test config: add downstream mTLS routes Add two new CA certificates for use with downstream mTLS tests, and a client certificate/key pair issued by each CA. Add a few routes to the policy template that require a client CA. Update the generated output configurations. (based on commit ed63a6a6e7) * add downstream mTLS integration test cases These are modeled after the tests added to v0.17 in 83957a9, but here the expected behavior is that requests with an invalid client certificate will receive a 495 response only after authentication.		2023-06-13 10:25:21 -07:00
..
ca-key.pem
ca.pem
client-key.pem
client.pem
downstream-1-client-key.pem	add downstream mTLS integration test cases (#4234)	2023-06-13 10:25:21 -07:00
downstream-1-client.pem	add downstream mTLS integration test cases (#4234)	2023-06-13 10:25:21 -07:00
downstream-2-client-key.pem	add downstream mTLS integration test cases (#4234)	2023-06-13 10:25:21 -07:00
downstream-2-client.pem	add downstream mTLS integration test cases (#4234)	2023-06-13 10:25:21 -07:00
downstream-ca-1.pem	add downstream mTLS integration test cases (#4234)	2023-06-13 10:25:21 -07:00
downstream-ca-2.pem	add downstream mTLS integration test cases (#4234)	2023-06-13 10:25:21 -07:00
invalid-key.pem
invalid.pem
pomerium-authorize-key.pem
pomerium-authorize.pem
pomerium-databroker-key.pem
pomerium-databroker.pem
rootCA-key.pem
rootCA.pem
signing-key.pem
trusted-key.pem
trusted.pem
untrusted-ca-key.pem
untrusted-ca.pem
untrusted-key.pem
untrusted.pem