Skip to content

Add multi-key support or user keys for providers (?) #36

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

Open
adewes opened this issue Dec 1, 2021 · 1 comment
Open

Add multi-key support or user keys for providers (?) #36

adewes opened this issue Dec 1, 2021 · 1 comment
Labels
discuss Issue for discussion, do not implement yet!

Comments

@adewes
Copy link
Member

adewes commented Dec 1, 2021

Currently providers use a single key pair for signing and encryption of data. When using Kiebitz within a larger organization it might be required to delegate access to many stakeholders, which should ideally have their own key pairs. To achieve this we could add multi-key support for providers, or we could add a user role to the system that has role-based access to the provider data. User keys would be generated in the frontend and signed by the provider key.

This would make key rotation / change for the provider keys less urgent as the keys would only be used for initial setup and user key generation and would not leave the device. Still, when revoking a given user key appointments signed with the key would need to be re-signed.

This issue is currently for discussion only, please do not implement this yet.

@adewes adewes changed the title Add multi-key support for providers (?) Add multi-key support or user keys for providers (?) Dec 1, 2021
@adewes adewes added the discuss Issue for discussion, do not implement yet! label Dec 1, 2021
@topialla
Copy link
Contributor

Is this truly still open? I though you had already added this functionality?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Issue for discussion, do not implement yet!
Projects
None yet
Development

No branches or pull requests

2 participants