-
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
Investigate recovery options for lost wallet keys #1012
Comments
As per @andrewwhitehead input, the sub-wallet records use this model and it might be possible to connect to the main wallet and and fetch records of type This could provide a good self-serve recovery option for users who have other ways of accessing the tenant (i.e.: api-key access) if:
I am thinking this would be a good addition for the innkeeper plugin, since it is already managing api-keys and we could therefore enhance functionality further. |
I attempted to create an innkeeper administrative endpoint that could be used to retrieve a tenant's wallet id/keypair in case of emergency: this is not (easily) feasible since the innkeeper is itself a tenant and accessing another sub-wallet is generally not a good idea. While a self-serve recovery option is possible, it will require having "privileged" access to the tenant via an "admin" api-key (see #1028). I am thinking this would be a better pattern especially since we (@loneil and I) have been discussing the possibility of not exposing the main keys at all to users requesting a new tenant, but rather providing them with tenant id/api-key combination to avoid potentially losing/leaking the main credentials (in which case a recovery endpoint might not even be necessary). Thoughts/opinions on this are welcome. |
We are likely pivoting towards providing tenants with tenant id and api-key rather than the "full" wallet keys. |
Investigate what can be done to recover lost wallet keys when in managed mode.
The text was updated successfully, but these errors were encountered: