Skip to content

Commit

Permalink
Add support for JWT signature algorithm ES384 (#160) (#161)
Browse files Browse the repository at this point in the history
The JWT signature algorithm wasn't supported, while RS384 was twice.
Without this algorithm some Kubernetes clusters can't authenticate.

Co-authored-by: Jeroen van den Heuvel <[email protected]>
  • Loading branch information
tomhjp and jeroenvdheuvel authored Sep 6, 2022
1 parent 7dfb33c commit 37e92c7
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion path_login.go
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ var defaultJWTIssuer = "kubernetes/serviceaccount"
// See https://datatracker.ietf.org/doc/html/rfc7518#section-3.
var supportedJwtAlgs = []capjwt.Alg{
capjwt.RS256, capjwt.RS384, capjwt.RS512,
capjwt.ES256, capjwt.RS384, capjwt.ES512,
capjwt.ES256, capjwt.ES384, capjwt.ES512,
}

// pathLogin returns the path configurations for login endpoints
Expand Down

0 comments on commit 37e92c7

Please sign in to comment.