Plesk 8,2 Modernbill 5.2 Automation Error

[Starchild]

Plesk 8.2 Modernbill 5.2 Automation Error

I am using the PleskWin panel in Modernbill (5.5. to connect to Plesk 8.2 for Windows and create clients and domains. Each time the scheduled task (cron) is run to do this the event fails due to a login error. I cannot determine the reason why to admin login fails. I have tested the login of course. The debug error text is below. Has any one run into this before? Thanks in advance for your help. The admin password and domain have been replaced for obvious reasons. Nevertheless, the password is a combination of upper and lower case letters, numbers, but NO special characters. The asterisks indicate the actual password length. Why does Plesk 8.2 not like the username/password combination? Am I using the correct username to access Plesks API from Modernbill? Should it be psaadm?
What is "errcode 1001".
*********************Debug Error Text************************
HTTP_AUTH_LOGIN: admin
HTTP_AUTH_PASSWD: ******************
HTTP_PRETTY_PRINT: TRUE
Content-Type: text/xml

<?xml version="1.0" encoding="UTF-8" standalone="no" ?><packet version="1.4.1.1"><server><get><stat/></get></server></packet>



Sent to: https://www.[domain]:8443/enterprise/control/agent.php


Plesk Win 8.2 (psa v8.2.0_build20070705.17 os_Windows 5.2.3790.0) Response:

<?xml version="1.0"?>
<packet version="1.4.1.1">
<system>
<status>error</status>
<errcode>1001</errcode>
<errtext>Login is incorrect.</errtext>
</system>
</packet>

 

[JackL]

Assuming that password and login you are using is correct, only problem can be name resolution . Try to send to IP address and check answer

john S.G.

 

[Starchild]

http://forums.modernbill.com/showthread.php?p=162560&posted=1#post162560

Thanks. Problem solved. The issue was in the length of the password!!!

Problem Solved!!!! Big giant thanks to the Modernbill Support staff for getting back in the trenches on this one. I cannot thank you guys enough. Huge kudos to John for taking the initiative and the time.

Anyone having problems with Plesk/Modernbill integration be advised that at the present time Plesk 8.2 will only accept a password with no more than 14 characters! The password supplied to Modernbill's API was 19 characters. As a result each time Modernbill tried to connect to Plesk the login failed and events were not run. Thanks again to John and his team for discovering this rather simple but critical factor. This password length issue isn't documented anywhere. Once again problem solved and now both Domains and Clients are being created in Plesk without error. Go Modernbill!!!

Hopefully, this issue with the password length will be addressed on the Plesk side. The funny part is that Plesk accepts any password length Modernbill ( in this case 19 characters) but then truncates it to the first 14 characters. The resulting stunted password fails to allow Modernbill to login into Plesk producing a "Login Failed" result in the MBAPI Output area. No where (at least no where that we could find) does it say that the maximum password length is 14 characters. That was the entire problem.

 

[sergius]

Hello Starchild,

Thank you very much for the report.
We will increase account's password length as soon as possible.

 

[Starchild]

You are welcomed

Your attention to this item is encouraging. I can only imagine how many others have lost precious time and money trying to get Modernbill and Plesk to talk. We are in a world where hackers, identity thieves, and organized criminal organizations are becoming more capable all the time. As an administrator I tend to create highly cryptic and long passwords. I was shocked when I realized that my 19-digit Plesk admin password was actually being truncated to the first 14 digits without any notification or alert or message regarding password length. One of the coolest things you might consider is 1) significantly increase the allowed password length (why not?), and 2) add a feature/component to measure or gauge password strength in both the admin and client login pages. Encourage and enable your customers to use stronger login/password pairs. Just some thoughts.