Skip to content
This repository has been archived by the owner on Aug 2, 2022. It is now read-only.

Implement Missing Permission Interface for EOSC #320

Closed
bytemaster opened this issue Sep 4, 2017 · 1 comment
Closed

Implement Missing Permission Interface for EOSC #320

bytemaster opened this issue Sep 4, 2017 · 1 comment
Assignees
@bytemaster
Milestone
EOS Dawn 1.0

Comments

@bytemaster
Copy link
Contributor 

eosc set account permission authority ${ACCOUNT} ${PERMISSION_NAME} ${AUTH} ?{PARENT_PERMISSION_NAME}
eosc set action permission ${ACCOUNT} ${CODE} ?{ACTION}  ${PERMISSION_NAME}

${AUTH} is a JSON blob containing an Authority structure.

if ${PERMISSION_NAME} is null then it should delete the link.
if ${PARENT_PERMISSION_NAME} is unspecified then it defaults to 'active'
@bytemaster bytemaster added this to the EOS Dawn 1.0 milestone Sep 4, 2017
@bytemaster bytemaster self-assigned this Sep 4, 2017
@nathanielhourt
Copy link
Contributor

Dupe: #185

@riotom riotom mentioned this issue Jun 6, 2018
Closed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bytemaster bytemaster

Labels
None yet
Projects
None yet
Milestone
EOS Dawn 1.0
Development

No branches or pull requests
2 participants
@nathanielhourt @bytemaster