Our customers need to sign transactions with a cryptographic key. We do not want to be in possession of this key. But our customers can not easily be trained to manage keys themselves. We need the keys to be managed for them, without us holding the keys.
To accomplish this, we will give each user a vault that will hold their keys and sign their transactions. The user will authorize an API access token for each transaction, that will temporarily allow us to request that the vault sign the transaction with the key. The token will be scoped to the specific transaction to be signed.
npm
package for interacting with the services in JavaScript.prvd --help
to verify the CLI is installed and to see what all it can do.You can create your application on any network.prvd networks list
will show your private networks andprvd networks list --public
will show available public networks.
The user ID should be persisted and associated with your record of your user.
The refresh token is also returned. It should be persisted and used to create future access tokens.
The organization ID should be persisted and associated with your record of your user.
The refresh token is also returned. It should be persisted and used to create future access tokens.
The vault ID should be persisted and associated with your record of your user.
The key ID should be persisted and associated with your record of your user.