Community Plugin: This plugin is developed, tested, and maintained by a third-party contributor.
This plugin will add a signed JWT into the HTTP Header
JWT of proxied requests through the Kong gateway. The purpose of this, is to provide means of Authentication, Authorization and Non-Repudiation to API providers (APIs for which Kong is a gateway).
API Providers need a means of cryptographically validating that requests they receive were proxied by Kong and not tampered with during transmission from Kong -> API Provider. This token accomplishes both as follows:
Authentication & Authorization - Provided by means of JWT signature validation. The API Provider will validate the signature on the JWT token (which is generating using Kong’s RSA x509 private key), using Kong’s public key. This public key can be maintained in a keystore, or sent with the token - provided API providers validate the signature chain against their truststore.
Non-Repudiation - SHA256 is used to hash the body of the HTTP request body, and the resulting digest is included in the
payloadhash element of the JWT body. API Providers will take the SHA256 hash of the HTTP Request Body, and compare the digest to that found in the JWT. If they are identical, the request remained intact during transmission.
$ luarocks install kong-upstream-jwt
$ git clone https://github.com/Optum/kong-upstream-jwt.git /path/to/kong/plugins/kong-upstream-jwt
$ cd /path/to/kong/plugins/kong-upstream-jwt
$ luarocks make *.rockspec
The plugin requires that Kong’s private key be accessible in order to sign the JWT. We also include the x509 cert in the
x5c JWT Header for use by API providers to validate the JWT. We access these via Kong’s overriding environment variables
KONG_SSL_CERT_KEY for the private key as well as
KONG_SSL_CERT_DER for the public key. The first contains the path to your .key file, the second specifies the path to your public key in DER format .cer file.
If not already set, these can be done so as follows:
$ export KONG_SSL_CERT_KEY="/path/to/kong/ssl/privatekey.key"
$ export KONG_SSL_CERT_DER="/path/to/kong/ssl/kongpublickey.cer"
One last step is to make the environment variables accessible by a nginx worker. To do this, simply add these line to your nginx.conf
Feel free to open issues, or refer to our Contribution Guidelines if you have any questions.
Enabling the plugin on a service
Enabling the plugin on a route
Enabling the plugin globally
A plugin which is not associated to any service, route, or consumer is
considered global, and will be run on every request. Read the
Plugin Reference and the Plugin Precedence
sections for more information.
Here's a list of all the parameters which can be used in this plugin's configuration:
|The name of the plugin to use, in this case
|The ID of the Service the plugin targets.
|The ID of the Route the plugin targets.
|Whether this plugin will be applied.
|The ID of the API the plugin targets.
Note: The API Entity is deprecated in favor of Services since CE 0.13.0 and EE 0.32.