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

solution for key store #823

Open
bytesun opened this issue Nov 20, 2024 · 1 comment
Open

solution for key store #823

bytesun opened this issue Nov 20, 2024 · 1 comment
Labels
question Further information is requested

Comments

@bytesun
Copy link
Contributor

bytesun commented Nov 20, 2024

For the case that app will integrate the 3rd party service, what is the way to store service key

@peterpeterparker peterpeterparker added the question Further information is requested label Nov 20, 2024
@peterpeterparker
Copy link
Contributor

On the IC or Juno, if you want to save a service key, the common approach is to store it in your backend—in Juno, this would be in a collection with permissions set as"controller." However, it's important to note that this approach is not entirely secure. For example, a compromised or malicious node provider could potentially access the canister's memory and extract the key.

Looking ahead, the VetKey proposal aims to offer some encoding mechanisms. However, based on its current design and what I heard, it appears to require the client to hold the private key, which may not be directly applicable for scenarios involving service keys.

In summary, it's probably acceptable to save keys in collections set as controllers if it does NOT require absolute, 100% security. For highly sensitive information, the risk of a compromised node provider accessing canister memory must be carefully considered.

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

No branches or pull requests

2 participants