ContainerImage.Pinniped/internal/controller/supervisorconfig/testdata/missing-active-jwks.json

{
  "keys": [
    {
      "use": "sig",
      "kty": "EC",
      "kid": "some-other-key",
      "crv": "P-256",
      "alg": "ES256",
      "x": "awmmj6CIMhSoJyfsqH7sekbTeY72GGPLEy16tPWVz2U",
      "y": "0"
    }
  ]
}
supervisor-generate-key: unit and integration tests Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-14 20:41:16 +00:00			`{`
			`"keys": [`
			`{`
			`"use": "sig",`
supervisor-generate-key: use EC keys intead of RSA EC keys are smaller and take less time to generate. Our integration tests were super flakey because generating an RSA key would take up to 10 seconds gasp. The main token verifier that we care about is Kubernetes, which supports P256, so hopefully it won't be that much of an issue that our default signing key type is EC. The OIDC spec seems kinda squirmy when it comes to using non-RSA signing algorithms... Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-15 15:33:08 +00:00			`"kty": "EC",`
supervisor-generate-key: unit and integration tests Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-14 20:41:16 +00:00			`"kid": "some-other-key",`
supervisor-generate-key: use EC keys intead of RSA EC keys are smaller and take less time to generate. Our integration tests were super flakey because generating an RSA key would take up to 10 seconds gasp. The main token verifier that we care about is Kubernetes, which supports P256, so hopefully it won't be that much of an issue that our default signing key type is EC. The OIDC spec seems kinda squirmy when it comes to using non-RSA signing algorithms... Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-15 15:33:08 +00:00			`"crv": "P-256",`
			`"alg": "ES256",`
			`"x": "awmmj6CIMhSoJyfsqH7sekbTeY72GGPLEy16tPWVz2U",`
			`"y": "0"`
supervisor-generate-key: unit and integration tests Signed-off-by: Andrew Keesler <akeesler@vmware.com> 2020-10-14 20:41:16 +00:00			`}`
			`]`
			`}`