Bug provider APIs are not all wrapped through the approval

[0xisk]

How to reproduce?

1. I changed the demo to have a button for directly calling one of the exposed RPC like GET_CONNECTED_IDENTITY_DATA through calling client.getConnectedIdentity()
2. I did step (1) without going trough client.connect() which has the approval step.
3. 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.

• Screenshot of the button Get Connected Identity
  

• Screenshot of the output data after clicking on Get Connected Identity
  

Tasks

Beta Give feedback

1. fix: refactoring createIdentity(), generateSemaphoreProof() and generateRLNProof() #897
   🛠 enhancement +1
   
2. fix: refactoring connect, disconnect and the ability to change connectedIdentity #898
   🛠 enhancement +1
   
3. fix: refactorig Bandada Provider APIs #899
   🛠 enhancement +1
   
4. fix: refactoring VC, and VP Provider APIs #900
   🛠 enhancement +1
   
5. fix: enhance the provider to be only with Post function #932
   +0