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
+9-6Lines changed: 9 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ To register a new local account:
90
90
```js
91
91
import { getLockKey } from"..";
92
92
93
-
var key =awaitgetLockKey({ addNewPasskey:true, });
93
+
var key =awaitgetLockKey({ addNewPasskey:true });
94
94
```
95
95
96
96
The returned keypair result will also include a `localIdentity` property, with a unique ID (`string` value) for the local account. This local account ID should be stored by your application (in local-storage, cookie, etc):
@@ -147,7 +147,7 @@ var key = Object.fromEntries(
147
147
If the `currentAccountID` (as shown above) is available, it should be used in subsequent calls to `getLockKey()` when re-obtaining the encryption/decryption keypair from the existing passkey:
148
148
149
149
```js
150
-
var key =awaitgetLockKey({ localIdentitity: currentAccountID, });
150
+
var key =awaitgetLockKey({ localIdentitity: currentAccountID });
151
151
```
152
152
153
153
If you don't have (or the application loses) an account ID, call `listLocalIdentities()` (async) to receive an array of all registed local account IDs.
@@ -161,7 +161,10 @@ Users may prefer a more robust security setup (less chance of identity/data loss
161
161
To prompt for adding a new passkey to an existing local account:
0 commit comments