-
Notifications
You must be signed in to change notification settings - Fork 55
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
Be able to import an existing DID Doc #542
Comments
I don't think we should promote moving private keys. It's safer to generate a new key in the service and have it added to an existing DID doc. |
Ok so to be clear, we wont support importing a private key? People bringing their own key wont be supported basically? I was hoping we could get this feature so we can import our key for our did web |
I'd recommend no. To support DID web let's add a new key to the doc that's managed by the service. So we can support an "import existing DID" flow. |
I agree that we shouldn't be moving private keys. Can you elaborate on what the "import existing DID" flow would do? |
Then you could have a key in the service that can act as the DID without having all keys in the document |
Be able to pull in the private key for issuing creds on existing cred:
example: https://www.tbd.website/.well-known/did.json
The text was updated successfully, but these errors were encountered: