OpenSRS API Integration for XML

Process Description
The only difference here is the value of the sender
attribute. Again, the only valid state at this point is
'ready'.
4 Reseller Client Client sends user data for authentication. This is done
using the XCP 'authenticate user' request.
Note: As a Reseller, you have a password and a
username. Do NOT send the password in this request,
it is not needed. The current XML Perl Client actually
sends the username in both the username and
password fields. This is because the data packets are
not encrypted at this stage of the transmission.
Perl Example (hash):
{
}
'protocol' => 'XCP',
'action' => 'authenticate',
'object' => 'user',
'attributes' => {
}
'crypt_type' => '',
'username' => '',
'password' => ''
The crypt_type can be either 'des' or 'blowfish'.
5 Reseller Agent If authentication is successful, the Reseller Agent
(server side), sends the first challenge, but without
XML. The challenge is a random number of random
bits.
6 Reseller Client Reseller Client The client returns the challenge's md5
checksum, encrypted with the Reseller's private key
and without XML.
7 Reseller Agent If the challenge is successful, the Reseller Agent
(server) replies with an XCP 'authenticate user'
response.
Perl Example (hash):
{
'protocol' => 'XCP',