Kong: a consumer-scoped plugin only runs after an auth plugin identified the consumer

Kong resolves consumer-specific configuration from the consumer set by an authentication plugin. Attach a per-consumer plugin to a route with no auth and it never matches, so the request falls through to the less specific config - or to none at all.

Full code & output

This topic is available to PRO members.

Sign in Create a free account

Run this yourself in the Online Java Compiler, spin up a live REST API in the API Sandbox, or practise with Java interview questions.

Published 2026-08-25