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 persistent CSR authorization database [service] #4

Open
allingeek opened this issue Jun 25, 2015 · 0 comments
Open

Implement persistent CSR authorization database [service] #4

allingeek opened this issue Jun 25, 2015 · 0 comments
Assignees
Milestone

Comments

@allingeek
Copy link
Owner

Currently the Pollendina service uses an in memory database (golang map) to store token=>CN authorizations. In order to support horizontal scaling of the Pollendina service and durability, some persistent or distributed database should be adopted.

A backend plugin infrastructure would be nice. That way adopters could use Consul, etcd, Redis, etc.

Alternatively, clustering could be embedded into the service for service-to-service memory sharing. One reason this may be preferred is that this is access control data. Securing the storage of the authorization content is at least as important as providing the authorization mechanism in the first place.

@allingeek allingeek self-assigned this Jun 25, 2015
@allingeek allingeek added this to the v0.1 milestone Jun 25, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant