Skip to content

Nocleye v0.4.0-beta release notes

v0.4.0-betabeta

OAuth2, token introspection and JWE authentication, scope rules, and a stricter rate limit caller identification.

Breaking

New authentication

Rate limit

Operations

Fixes

Before, a route with usage control and no client ID rule counted callers by IP. Now there is no default: any client ID rule other than IP is used as the caller id, and a request whose id can’t be collected is refused with 401 and Missing identification value.

To keep counting by IP, define an IP rule and bind it, for example on GlobalConfig:

gateway.yaml
Rules:
ClientIDRules:
by-ip:
Modes: [IP]
GlobalConfig:
ClientIDRule: by-ip

To keep a rule that reads a header or token but still count callers that don’t send it, set IfMissingUseIP:

gateway.yaml
Rules:
ClientIDRules:
by-customer:
Modes: [CustomHeader]
HeaderCustomValue: X-Customer-Id
IfMissingUseIP: true

A route with usage control rules and no way to identify callers is now an error, and so is a client ID rule without Modes. Run nocleye check on your config before you upgrade. See Client ID rules.

Pick a binary or the Docker image on Downloads and verification, then follow Getting started.