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

IDSA keys storage in k8s secrets #15

Open
c0c0n3 opened this issue Jan 9, 2020 · 3 comments
Open

IDSA keys storage in k8s secrets #15

c0c0n3 opened this issue Jan 9, 2020 · 3 comments
Assignees
Labels
enhancement New feature or request

Comments

@c0c0n3
Copy link
Member

c0c0n3 commented Jan 9, 2020

At the moment both pub and private keys sit in the adapter config. While it's okay for the pub key to be there, we should find a better home for the private key---think raising the bar for security. Figure out if Istio Citadel could help here or should we rather use K8s secrets/tmpfs volumes? Any other options?

The advantage of adapter config storage is access speed and caching. We should consider these two factors too when scratching around for a solution.

@c0c0n3 c0c0n3 added this to the End February Release milestone Jan 9, 2020
@c0c0n3 c0c0n3 added the enhancement New feature or request label Jan 9, 2020
@chicco785
Copy link

chicco785 commented Jan 9, 2020 via email

@gboege
Copy link
Collaborator

gboege commented Jan 10, 2020

I would go for the more docker/k8s solution. To make it easier to understand in the first run. If we face performance issues, we should have it in mind.

@c0c0n3
Copy link
Member Author

c0c0n3 commented Jan 10, 2020

If my memory serves me well, K8s secret volumes get mounted on a tmpfs which is normally RAM- backed. So key look up should be darn fast...well, at least that's the theory, time will tell :-)

@gboege gboege changed the title IDSA keys storage IDSA keys storage in k8s secrets Jan 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants