If you reuse this article in your ticket, ask the customer why it is important for them to use additional admin account for API instead of built-in admin user. Forward the customer's response to @ipostnikov
Executing REST API request to Plesk server under additional administrator account fails:
"message": "Can not find client by login 'johndoe'"
Plesk REST API limitation: requests cannot be executed under Plesk additional administrator accounts.
The item for improvement with ID EXTREST-87 was created to implement this functionality.
Until the functionality is implemented, execute the API request using built-in "admin" Plesk account instead, for example:
# curl -k -u admin:password -X POST -d @domain.json "https://203.0.113.2:8443/api/v2/domains"
Is there already a update regarding this issue?
Do you have an update that resolves this issue?
we are also waiting eager for this Bug to be fixed. Any ETA on this as Customers of our Plesk Servers are waiting for this ...
Hello Daniel Broen, Ralph Otowo and Andreas Schnederle-Wagner
Could you please describe your use-cases? Why do you need to use additional Plesk administrator accounts for API instead of built-in 'admin' user?
In addition, there are different authentication methods in REST API, one of them is API keys - https://docs.plesk.com/en-US/obsidian/api-rpc/about-rest-api.79359/#authentication-methods. Does it anyhow help you in your scenarios?
@... - haven't seen your reply earlier.
Our Use-Case - we are Service Provider, on the Plesk Servers for our Customers we keep the "Main Admin" Account with "our Password" and Customer get additional Plesk Admin Account.
Some of our Customers are using the API ... there is the Problem ... they can't use the API with their Admin User ...
This tweak would be very important for us, I will describe our use case:
We have plesk servers with thousands of websites, but all of them are managed by our agency.
Also, we have many programmers, and each one has an admin alias login, for logging and login control purposes.
As we manage many websites, our team of programmers create several robots that automate various processes, such as updating the php version, plugins, cleaning, optimizations, security, etc.
Currently, as only I have the global admin password, for each new robot I need to personally create a key for that person and control it through the 'description' , but I would like them to be able to create it with their own users.
This is my use case, but I can think of many others, like the ones mentioned above, so I believe it is an important feature.
Thank you very much for your attention!
Please sign in to leave a comment.