OS : CENTOS 7.4 kvm
cPanel : v68.0.29
When issuing the command:
The command returns:
Using the api_token_list command, I see all the acls that the token has now and it includes 'all'
However, when you view the token's permissions from inside WHM, the token does not have 'all' applied and the token does not actually have the permission either. ( cPanel API Response: You do not have permission to create sessions for the user <user> )
If I use the API shell and issue the same command, the command does correctly set the acl and the user is allowed to create sessions for another user.
So - question: is there a cPanel service I need to restart after I use the whmapi1 command to get the system to pick up the new acl? Is this a bug?
cPanel : v68.0.29
When issuing the command:
Code:
whmapi1 api_token_update token_name=<tokenname> acl-1=all
Code:
data:
acls:
- all
create_time: '1518471368'
name: <tokenname>
metadata:
command: api_token_update
reason: OK
result: 1
version: 1
However, when you view the token's permissions from inside WHM, the token does not have 'all' applied and the token does not actually have the permission either. ( cPanel API Response: You do not have permission to create sessions for the user <user> )
If I use the API shell and issue the same command, the command does correctly set the acl and the user is allowed to create sessions for another user.
Code:
{"metadata":{"version":1,"result":1,"command":"api_token_update","reason":"OK"},"data":{"create_time":1518534128,"acls":["all"],"name":"tokenname"}}