Missing X-Consumer in Upstream Headers

Forgive me for being such a noob, but how do I get Kong to send the X-Consumer fields in the upstream headers? Currently, I am only getting the apikey (see below), but per the documentation, I would expect more.
{
“accept”: “/”,
“apikey”: “XXXXXXXX074a”,
“connection”: “keep-alive”,
“content-length”: “641”,
“content-type”: “application/json”,
“host”: “localhost:3000”,
“user-agent”: “curl/7.29.0”,
“x-forwarded-for”: “XX.XX.XXX.XXX”,
“x-forwarded-host”: “api.myhost.com”,
“x-forwarded-port”: “443”,
“x-forwarded-proto”: “https”,
“x-real-ip”: “XX.XX.XXX.XXX”
}

I am a newbie too. Just wanted to help out from my little experience.
Have you set up the key-auth plugin for the apis? If the api gets matched and key-auth passes then the X-Consumer fields start appearing. May be you can share some details of the set up.

2 Likes

Thanks, @root-three! I think that in the process of reinstalling Cassandra, Kong lost the key-auth plugin. Regardless of the root cause, thanks for pointing out that I was missing the key-auth plugin.