Skip to content
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

Implement better API Key security #36

Open
whitlockjc opened this issue Aug 20, 2016 · 1 comment
Open

Implement better API Key security #36

whitlockjc opened this issue Aug 20, 2016 · 1 comment

Comments

@whitlockjc
Copy link
Contributor

whitlockjc commented Aug 20, 2016

When it comes to applications, security is up to them. But the k8s-router does allow you to have some level of security in that you need an API Key to access your deployments. Thankfully this is opt-in and not required but for those that do want it, we need a better solution. Right now the keys are static and created at the namespace level. It would be nice to give the deployment owner more control as to which key(s) to use.

While this is not to be confused with authentication as a service, we could eventually turn this into a lightweight, API Management feature supporting more than just simple keys.

@whitlockjc
Copy link
Contributor Author

The ability to do this in the future might depend on Dibyo's KVM stuff.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant