-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
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
Support BasicAuth and KeyAuth based authentication #1660
Comments
This issue has been automatically marked as stale because it has not had activity in the last 30 days. |
thinking out loud
and something similar could be done for API Key as well |
@arkodg AFAIK, Envoy doesn't have built-in BasicAuth or API key support. But it may be accomplished by extensions such as lua, wasm, or External Authorization. |
Basic Auth has been merged into Envoy. envoyproxy/envoy#30079. I plan to add it to the SecurityPolicy in the next release. |
@zhaohuabing can we reuse the same Envoy Filter for API key auth ? |
The problem is, unlike HTTP Basic Auth, API key auth is much more flexible, the key can be in the header, path, or even body. I think we will need a dedicated envoy filter in Envoy if we want to support API key auth, we can follow the open API specs: https://swagger.io/docs/specification/authentication/api-keys/#:~:text=API%20keys%20are%20supposed%20to,mechanisms%20such%20as%20HTTPS%2FSSL. |
yeah nice, it would look a lot like |
Key auth is not supported yet. We can open another issue to track it. |
1 similar comment
Key auth is not supported yet. We can open another issue to track it. |
Description:
Support BasicAuth and KeyAuth based authentication
[optional Relevant Links:]
envoyproxy/envoy#15365
The text was updated successfully, but these errors were encountered: