search

greymass / anchor

EOSIO Desktop Wallet and Authenticator
https://greymass.com/anchor/
MIT License
568 stars 221 forks source link

Handling custom permissions #304

Open DenisCarriere opened 6 years ago

DenisCarriere commented 6 years ago

Not sure if this is implemented yet, it would be nice to sign transactions using a different permission, able to replace the default active.

image

default permission

"authorization": [
  {
    "actor": "<ACCOUNT>",
    "permission": "active"
  }
]

custom permission

"authorization": [
  {
    "actor": "<ACCOUNT>",
    "permission": "custom"
  }
]
aaroncox commented 6 years ago

Totally agreed. We have a lot of the UI for this built out already, but I think we're going to hold off on the 0.5.0 implementation until we get to a point where we can actually lookup what actions those auths provide and a change to eosjs that allows a global flag for which auth to use.

aaroncox commented 6 years ago

Partially completed in now (0.5.1) in that whatever authorization a key has, that's what will be passed to the eosjs instance for signing. Still no UI to manage those authorizations though.

DenisCarriere commented 6 years ago

Awesome! Looking forward to this 😄