Signing ops with custom json needing active auth (required_auths: [...]) uses posting
eonwarped opened this issue · comments
Expected behavior
For ops that have custom jsons needing active auth, the generated hive signer url is not detecting the need to use posting it seems:
Actual behavior
Registers as needing posting:
Steps to reproduce the behavior
Go to url:
Just to note what I mentioned in our chat, it can be done like this for now and you can use redirect_uri at the end as callback parameter as well. We will add auto detection for authority requirement for custom json in upcoming updates.
http://hivesigner.com/sign/custom_json?authority=active&required_auths=demo&id=ssc-mainnet-hive&json={%22contractName:%22tokens%22,%22contractAction%22:%22transfer%22...}
For future reference: Here is working example, note that required_posting_auths should have empty array and required_auths should have array of account whose active key is requested to sign the transaction.
https://hivesigner.com/sign/custom_json?authority=active&required_auths=["demo123"]&required_posting_auths=[]&id=ssc-mainnet-hive&json={"contractName":"tokens","contractAction":"transfer","contractPayload":{"symbol":"LEO","to":"eonwarped","quantity":"0.001","memo":""}}