The Key Authentication plugin adds an API key to your APIs. Consumers then add their key either in a querystring parameter or a header to authenticate their requests. It’s currently stable and works with Kong CE and Kong EE. Give it a try and discuss it here!
Does a consumer’s apikey allow them access to any route/service in the workspace, or can you limit to specific routes? Example: consumer A can access route 1 and route 2, consumer B can only access route 1.