This repository has been archived by the owner on May 7, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 826
can not change key names in key-auth plugin #33
Comments
Thank you for the hints, @pantsel |
Kong doesn't provide a default key name in case you don't define one. I am wondering where did this "function" thingy you mentioned came from. It is probably returned from Kong's admin API. I will check it out and handle it properly if that's the case. |
According to [this page](
https://getkong.org/docs/0.10.x/getting-started/enabling-plugins/), it says:
Note: This plugin also accepts a config.key_names parameter, which
defaults to [apikey].
from Dr. Lu Liu's Nexus phone
2017年3月22日 10:29,"Panagis Tselentis" <notifications@github.com>写道:
… Kong doesn't provide a default key name in case you don't define one.
I am wondering where did this "function" thingy you mentioned came from.
It is probably returned from Kong's admin API.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#33 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ABfckJOsVmkpf3kH7HF5MDQLFP9jqbQ-ks5roOnjgaJpZM4MidUr>
.
|
OK! It seems i didn't get that right. Thanks again! |
hainguyen8y
pushed a commit
to hainguyen8y/konga
that referenced
this issue
Aug 19, 2022
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When creating or changing a
key-auth
plugin, thekey names
field does not work. It will keep blank no matter what I fill in. It seems that it has a default valuefunction
. But I am not sure. This is the request body after clicking thesubmit changes
button:And the response:
Actually, I met this already in version 0.4
The text was updated successfully, but these errors were encountered: