You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+69-6
Original file line number
Diff line number
Diff line change
@@ -4,40 +4,101 @@
4
4
# ethersjs-azure-keyvault-signer
5
5
An Ethers.js compatible signer that connects to Azure Key Vault
6
6
7
+
<br/>
8
+
7
9
# Installation
8
10
Install the azure keyvault signer library using npm
9
11
10
12
`npm install ethersjs-azure-keyvault-signer`
11
13
14
+
<br/>
15
+
12
16
# Background
13
17
- Current web3 signers only support keys managed by the users directly in the form of browser wallets like Metamask, WalletConnect, Hardware wallets or self managed keys.
14
18
- Enterprises prefer to maintain the private keys in a secured key store like Azure Key Vault rather than letting their employees handle their private keys.
15
19
- Private keys generated and stored in key stores like Azure Key Vault/HSM are never exposed directly to the users. Interaction with such keys is done via SDKs developed by the respective key stores.
16
20
- Our library allows enterprise users to interact with dapps without having to deal with browser wallets or the hassle of managing keys
17
21
- It enables the user to perform cryptographic operations like signing messages and transactions stored in their enterprises' Azure Key Vault or Managed HSM
18
22
19
-
## Azure Key Vault Credentials Interface
23
+
<br/>
20
24
21
-
Authentication to Azure Key Vault can be done either using client secret or client certificate.
25
+
# Azure Key Vault Credentials Interface
22
26
23
-
> Note: The client certificate should be a .pem encoded file with unencrypted private key included.
27
+
Authentication to Azure Key Vault can be done either using client secret, client certificate or access token(with the Key Vault scope).
0 commit comments