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
..
apicerts	Do not rotate impersonation proxy signer CA unless necessary	2021-10-06 12:03:49 -04:00
authenticator	Force the use of secure TLS config	2021-11-17 16:55:35 -05:00
conditionsutil	Split package upstreamwatchers into four packages	2021-05-12 14:00:39 -07:00
impersonatorconfig	Do not rotate impersonation proxy signer CA unless necessary	2021-10-06 12:03:49 -04:00
issuerconfig	When merging CredentialIssuer updates, don't overwrite LastUpdated.	2021-05-27 17:09:12 -05:00
kubecertagent	Force the use of secure TLS config	2021-11-17 16:55:35 -05:00
supervisorconfig	Force the use of secure TLS config	2021-11-17 16:55:35 -05:00
supervisorstorage	Add leader election middleware	2021-08-20 12:18:25 -04:00
controller_test.go	Clean this test up a trivial amount using require.Implementsf().	2020-12-17 08:38:16 -06:00
utils.go	Upstream Watcher Controller Syncs less often by adjusting its filters	2020-12-18 15:41:18 -08:00