We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Plugin basic-auth doesn't have required field currently.
basic-auth
required
apisix version
None
No required field.
It should have at least one required field such as username or password in my opinion.
The text was updated successfully, but these errors were encountered:
For all of the authorization plugin:
When it was used with consumer, it is necessary to provide specific authentication information.
consumer
When it was used with route / service, we don't need any parameters, just enable or disable this plugin.
route / service
So I think the current way is right.
How about this schema definition? Is it better?
schema
oneof = { -- no parameter required = {}, -- two parameters required = {"username", "passwd"} }
Sorry, something went wrong.
bugfix: the plugin basic-auth needs required field (#1251)
834e9e1
Fix #1244
bugfix: the plugin basic-auth needs required field (apache#1251)
74b04c6
Fix apache#1244
membphis
Successfully merging a pull request may close this issue.
Issue description
Plugin
basic-auth
doesn't haverequired
field currently.Environment
apisix version
):Minimal test code / Steps to reproduce the issue
None
What's the actual result? (including assertion message & call stack if applicable)
No
required
field.What's the expected result?
It should have at least one required field such as username or password in my opinion.
The text was updated successfully, but these errors were encountered: