Skip to content

Simple service that validates jwt tokens and answer 200 or 401

License

Notifications You must be signed in to change notification settings

bennesp/jwt-forward-auth

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

23 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Jwt µService

Simple http server that can receive a JWT in the http request and answer with a 200 if the JWT is valid, 401 otherwise.

It implements both JWKS (with both asymmetric RSA/ECDSA/... keys and symmetric OCT keys) and SECRET modes.

It can read jwt from headers and cookies and it can be extended to read it from anywhere (just write a sources/source.go file).

Can be used in conjunction with traefik and forwardAuth middleware (See examples/kubernetes).

Quick Start

You can test all the examples with something like: curl -vv -H "Authorization: Bearer eyJraWQiOiJiZGM4N2Y2YyIsInR5cCI6IkpXVCIsImFsZyI6IkVTMjU2In0.eyJzdWIiOiJEaW1pdHJ5IiwiYXVkIjoiUnVzbGFuIiwiaXNzIjoiandrcy1zZXJ2aWNlLmFwcHNwb3QuY29tIiwiaWF0IjoxNjM5MTc4NTIyfQ.h9l2jd_kV33NQ8ygqsqAyi0iwhR_8bTp8fObRhB-BJ1xkItA2VIb135ww1BNmzMaL4Hs6FO553oJkmfwnYhx-Q" localhost:8080

With docker

docker run --rm -ti -e JWKS_URL='https://jwks-service.appspot.com/.well-known/jwks.json' -e JWKS_REFRESH_UNKNOWN_KID=false -p 8080:8080 ghcr.io/bennesp/jwt-forward-auth:latest

With docker-compose

# docker-compose.yaml
services:
  jwt:
    image: ghcr.io/bennesp/jwt-forward-auth:latest
    ports:
      - "8080:8080"
    environment:
      - JWKS_URL='https://jwks-service.appspot.com/.well-known/jwks.json'

and docker-compose up -d

With kubernetes

See examples/kubernetes

Environment variables

General

  • ADDRESS (default is :8080): address where the http server will listen to
  • LOG_LEVEL (default is info): one between trace, debug, info, warn or warning, error, fatal, and panic
  • CLAIM_MAPPINGS (default is sub:x-jwt-user-id,iss:x-jwt-issuer): a comma separated list of claim mappings, where the first one is the claim name in the JWT and the second one is the header name to be used in the http response

Read JWT from a header

  • HEADER_JWT_SOURCE_ENABLED (default is true): If true, header source is enabled
  • HEADER_JWT_SOURCE_NAME (default is Authorization): Name of the header whose value is the jwt
  • HEADER_JWT_SOURCE_PREFIX (default is Bearer ): If the value of the header is prefixed by a value, specify it with this environment variable so that it will be trimmed. If a value is specified but it is not found in the header, no errors will be thrown and no value will be trimmed.

Read JWT from a cookie

  • COOKIE_JWT_SOURCE_ENABLED (default is false): If true, cookie source is enabled
  • COOKIE_JWT_SOURCE_NAME (default is token): Name of the cookie whose value is the jwt

Validate JWT with JWKS

  • JWKS_ENABLED (default is true): If true, validation with JWKS is enabled
  • JWKS_URL (default is ""): URL of the keys of your IdP. For example https://jwks-service.appspot.com/.well-known/jwks.json
  • JWKS_REFRESH_INTERVAL (default is 1h): Interval between the refresh of the keys. Disable setting it to 0.
  • JWKS_REFRESH_RATE_LIMIT (default is 5m): Rate limit for the refresh of the keys. Max refresh interval (if JWKS_REFRESH_UNKNOWN_KID is true). Does not make sense to have JWKS_REFRESH_INTERVAL shorter than this.
  • JWKS_REFRESH_TIMEOUT (default is 5s): Timeout for the refresh of the keys.
  • JWKS_REFRESH_UNKNOWN_KID (default is true): If true, unknown kid will be refreshed.

Validate JWT with a secret

  • JWT_SECRET_ENABLED (default is false): If true, validation with a secret is enabled
  • JWT_SECRET (default is ""): Secret used to sign and verify the JWT.

About

Simple service that validates jwt tokens and answer 200 or 401

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages