-
Notifications
You must be signed in to change notification settings - Fork 8
Description
How to reproduce?
- I changed the demo to have a button for directly calling one of the exposed RPC like
GET_CONNECTED_IDENTITY_DATA
through callingclient.getConnectedIdentity()
- I did step (1) without going trough
client.connect()
which has the approval step. - I did get output showing the connected identity metadata.
How to resolve?
I think all the exposed APIs should be handling the Approval part internally inside the background script. Which means that all the RPC calls inside the Provider are protected from inside the extension.
### Tasks
- [ ] https://github.com/CryptKeeperZK/crypt-keeper-extension/issues/897
- [ ] https://github.com/CryptKeeperZK/crypt-keeper-extension/issues/898
- [ ] https://github.com/CryptKeeperZK/crypt-keeper-extension/issues/899
- [ ] https://github.com/CryptKeeperZK/crypt-keeper-extension/issues/900
- [ ] https://github.com/CryptKeeperZK/crypt-keeper-extension/issues/932
Metadata
Metadata
Assignees
Labels
🪲 bugSomething isn't workingSomething isn't working
Type
Projects
Status
👀 Review / QA