The purpose of this package is to provide a
jwt.Keyfunc
for the
github.com/golang-jwt/jwt/v5 package using a JSON Web Key Set (JWK Set) for parsing
and verifying JSON Web Tokens (JWTs).
It's common for an identity providers, particularly those
using OAuth 2.0
or OpenID Connect, such
as Keycloak
or Amazon Cognito (AWS) to expose a
JWK Set via an HTTPS endpoint. This package has the ability to consume that JWK Set and produce a
jwt.Keyfunc
. It is important that a JWK Set endpoint is
using HTTPS to ensure the keys are from the correct trusted source.
For complete examples, please see the examples
directory.
import "github.com/MicahParks/keyfunc/v3"
The below example is for a remote HTTP resource.
See examples/json/main.go
for a JSON
example.
// Create the keyfunc.Keyfunc.
k, err := keyfunc.NewDefaultCtx(ctx, []string{server.URL}) // Context is used to end the refresh goroutine.
if err != nil {
log.Fatalf("Failed to create a keyfunc.Keyfunc from the server's URL.\nError: %s", err)
}
When using the keyfunc.NewDefault
function, the JWK Set will be automatically refreshed using
jwkset.NewDefaultHTTPClient
. This does launch a "
refresh goroutine". If you want the ability to end this goroutine, use the keyfunc.NewDefaultCtx
function.
It is also possible to create a keyfunc.Keyfunc
from given keys like HMAC shared secrets. See examples/hmac/main.go
.
// Parse the JWT.
parsed, err := jwt.Parse(signed, k.Keyfunc)
if err != nil {
log.Fatalf("Failed to parse the JWT.\nError: %s", err)
}
This project's primary purpose is to provide a jwt.Keyfunc
implementation for JWK Sets.
Since version 3.X.X
, this project has become a thin wrapper
around github.com/MicahParks/jwkset. Newer versions contain a superset of
features available in versions 2.X.X
and earlier, but some of the deep customization has been moved to the jwkset
project. The intention behind this is to make keyfunc
easier to use for most use cases.
Access the jwkset.Storage
from a keyfunc.Keyfunc
via
the .Storage()
method. Using the github.com/MicahParks/jwkset package
provides the below features, and more:
- An HTTP client that automatically updates one or more remote JWK Set resources.
- An automatic refresh of remote HTTP resources when an unknown key ID (
kid
) is encountered. - X.509 URIs or embedded certificate chains, when a JWK contains them.
- Support for private asymmetric keys.
- Specified key operations and usage.
A JWK Set implementation. The keyfunc
project is a wrapper around this project.
A JWK Set client proxy. JCP for short. This project is a standalone service that uses keyfunc
under the hood. It
primarily exists for these use cases:
- The language or shell a program is written in does not have an adequate JWK Set client. Validate JWTs with
curl
? Why not? - Restrictive networking policies prevent a program from accessing the remote JWK Set directly.
- Many co-located services need to validate JWTs that were signed by a key that lives in a remote JWK Set.
If you can integrate keyfunc
directly into your program, you likely don't need JCP.