editpkg using URL api call error

[Camilo Herrera]

Hello Guys,

I am testing the package edit API Update hosting plan as root using cURL and it shows an error message as follows:

(XID sxaa59) “_modpkg” requires a package name that you have permission to access.

Don't try to use the CLI API call, that one works just fine. It is the URL API call that shows this behavior. The package name has no "root_" prefix (and it shouldn't), do you know what is going on there?, i have seen a post from 2020 that does not help and everyone just went silent on it without an answer.

Can not edit package via api if it not begins with root_ in name

Hi, I have root access to my server, and I want to edit packages using the WHM API, but I am having the error “_modpkg” require a package name that you have permission to access. If the package_name starts with root_ I am allowed to edit it; also, if I create a package using api, it starts...

forums.cpanel.net

If anybody knows how to avoid this, workaround or fix, that would be great. I expected that the CLI call and URL call would behave the same, but here i am.

 

[cPRex]

Hey there! Can you post the exact URL call you're using so I can do some more testing?

 

[Camilo Herrera]

Hey!, yes, this is the URL call "https://xxx.xxx.xxx.xxx:2087/json-api/editpkg?api.version=1&name=Personal&bwlimit=5000&quota=2000"

 

[cPRex]

Running that worked well on my end - I used this command in an active session:

https://172.105.107.152:2087/cpsess4498069613/json-api/editpkg?api.version=1&name=testing&bwlimit=1000

and I received this output:

{"data":{"pkg":"testing"},"metadata":{"command":"editpkg","reason":"OK","version":1,"result":1}}

I also tried with the "&quota" option as well, and that worked fine for me also.

I did an addition test since you note your package is named "Personal" and did confirm that the package name is case-sensitive, so maybe that is related to the issue? But at this time, I can't reproduce the problem on my end.

You're always welcome to create a ticket with our team so we can check this directly on your system.

 

[Camilo Herrera]

I am using a token (root user) and sending the authentication info on the "Authorization" header to execute the command, it may be related to the authentication method, it works just fine on CLI too.

If possible try creating a token and then using curl from the command line as suggested on the post mentioned on the first message, like this:

curl -XGET -H 'Authorization: whm root:MYTOKEN' -d 'api.version=1&name=testing&bwlimit=1000' 'https://172.105.107.152:2087/json-api/editpkg'

 

[cPRex]

I tested this with a token on my end just now, and that method is also working well for me. Could you submit a ticket so we can check the affected system?

 

[Camilo Herrera]

Guess i found the cause, did you checked the "Everything->All Features" privileges for the token, right?, uncheck it and try again (keep the remaining privileges checked).

The question is, why do you have to give the token access to all privileges if you have a "Packages Standard Privileges->Add/Remove Packages add-pkg" and "Packages Standard Privileges->Edit Packages edit-pkg" section on the permission list?. It may be misleading.

 

[cPRex]

I didn't have the "all" option checked on my end, and I wouldn't expect that to be required for that particular action.

 

[Camilo Herrera]

Once i checked that privilege the call worked, that's weird.

 

[cPRex]

It's weird for sure - you can always put in that ticket and we'll check it out!