-
Notifications
You must be signed in to change notification settings - Fork 593
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
mTLS Kong Admin API authentication support #1958
Comments
Feature request proposal related to mTLS Kong Admin API authentication support Kong#1958
@ludovic-pourrat the PR for this timed out due to inactivity, would you want that re-opened? Is there any additional assistance you need from us to continue it? |
I will work on it next week. sorry for the delay. |
No worries, thanks for the update and please let us know how we can help. Whenever you're ready to get back to it, feel free to just "re-open" the PR 👍 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Feature request proposal related to mTLS Kong Admin API authentication support Kong#1958 Updated according feedback.
Review test definition.
About readability.
Add error management.
Add documentation.
Make linter more happy again.
Last one missed.
Try to fix the linter.
Missing spaces in error logs.
Is there an existing issue for this?
Problem Statement
This is a new feature request to support Kong mTLS authentication capabilities.
Kong API administration API can be secured via mTLS authentication by setting the following NGINX directives,
Thus, the ingress controller should provide a way to specify client certificates.
Proposed Solution
Add new arguments to specify the client certificate and key and setup the http/client package to use client certificates.
Additional information
No response
Acceptance Criteria
Once mTLS activated the ingress controller should authenticate to Kong administrative API with the specified client certificate and key.
The text was updated successfully, but these errors were encountered: