Resolved xml api creat role for user deprecated

[christian]

i used xml api to create role to additional user in plesk 12.5., to give them right to manage customers emails on her website. working perfectly in 12.5
but
after upgrading to version 17, the xml api don't want to make the job.

i followed the minimal sample at Creating a Role
but give Error:'This feature is no longer supported.'
what the hell. ??

where is the right doc? how to do this,? to give right to user to manage emails or other.?

 

[IgorG]

About XML API

No Longer Supported Operators
The support for the following rarely used operators and stub operators was removed in Plesk Onyx 17.8:
....
role
....

Now it's better to use REST API - How to manage Plesk via REST API?

 

[christian]

ok, so, to resume.
you was deleted part of xm apî, because you determinate , on your side , simply, that is rarely used. thanks for customer that use it. !!!
and replaced by ??? NOTHING..!!
you api rest V2 contain nothing to manage right for customer account.
thank you to wrecked our work and automation process !!
ARE YOU A PARTNER OR AN ENNEMY ??

 

[IgorG]

and replaced by ??? NOTHING..!!
you api rest V2 contain nothing to manage right for customer account.

What about something like:

# curl -ikX POST -H "Content-Type: application/json" -u adminassword "https://xxx.xxx.xxx.xxx:8443/api/v2/cli/role/call" -d'{"params":["--create", "test_role", "-owner", "admin", "-webSitesAndDomainsManagement", "true"]}'

?

 

[Alban Staehli]

Encountering same issue here - was used to the user/add packet through XML API. Any alternative?

 

[IgorG]

Any alternative?

As I wrote above - REST API.

 

[Alban Staehli]

Yep, ended up with this and it works well:

curl -k -X POST -u 'admin:PaSSword' "https://IP_ADDRESS:8443/api/v2/cli/user/call" -H "accept: application/json" -H "Content-Type: application/json" -d '{ "params": [ "-c", "myUsername", "-role", "myRole", "-passwd", "PaSSword!", "-cname", "myName", "-email", "[email protected]", "-subscription-name", "mysubcription.domain.tld", "-owner", "myOwnerUsername", "-locale", "fr-FR" ]}'

 

[Alban Staehli]

https://IP_ADDRESS:8443/api/v2/cli/user/call now returns 404... based on the Swagger, there's no more user/call...
Any alternative?

 

[Alban Staehli]

https://IP_ADDRESS:8443/api/v2/cli/user/call now returns 404... based on the Swagger, there's no more user/call...
Any alternative?

Solved.... after playing around, the trailing slash was the issue. No clue why it changed, maybe a change in PHP version of the script calling the API...

In brief:

• https://<IP_ADDRESS>:8443/api/v2/cli/user/call/ returns 404
• https://<host.domain.tld>:8443/api/v2/cli/user/call/ returns 404
• https://<IP_ADDRESS>:8443/api/v2/cli/user/call all good
• https://<host.domain.tld>:8443/api/v2/cli/user/call all good