Monis Khan cd686ffdf3 Force the use of secure TLS config ... This change updates the TLS config used by all pinniped components. There are no configuration knobs associated with this change. Thus this change tightens our static defaults. There are four TLS config levels: 1. Secure (TLS 1.3 only) 2. Default (TLS 1.2+ best ciphers that are well supported) 3. Default LDAP (TLS 1.2+ with less good ciphers) 4. Legacy (currently unused, TLS 1.2+ with all non-broken ciphers) Highlights per component: 1. pinniped CLI - uses "secure" config against KAS - uses "default" for all other connections 2. concierge - uses "secure" config as an aggregated API server - uses "default" config as a impersonation proxy API server - uses "secure" config against KAS - uses "default" config for JWT authenticater (mostly, see code) - no changes to webhook authenticater (see code) 3. supervisor - uses "default" config as a server - uses "secure" config against KAS - uses "default" config against OIDC IDPs - uses "default LDAP" config against LDAP IDPs Signed-off-by: Monis Khan <mok@vmware.com>		2021-11-17 16:55:35 -05:00
..
cluster_capabilities	Run the LDAP client's integration tests only on Kind	2021-07-08 11:10:53 -07:00
deploy/tools	Optionally allow OIDC password grant for CLI-based login experience	2021-08-12 10:45:39 -07:00
integration	Force the use of secure TLS config	2021-11-17 16:55:35 -05:00
testlib	Force the use of secure TLS config	2021-11-17 16:55:35 -05:00