Page 34 of the new API spec states:
The Contact object in OpenSRS is really great.
Well, I would say it would be if I could get it to work, so i could actually
fix the problem noted that existing users information is not pre-populated
in the new SSL order form. (After all, why bother to have a user choose a
username/password if there is nothing to gain by having done so - why not
just autogenerate one for them!)
Page 34 states:
Contacts permit the following actions to be performed:
create (not yet available)
query
update
delete (not yet available)
transfer (not yet available)
I coded a test Perl program to see if I could get the query function to
work, containing the code:
my $request2 = {
protocol => 'TPP',
action => 'query',
object => 'contact',
requestor => {
username => $OPENSRS{username}
},
attributes => {
id => '000', #I ACTUALLY USE A REAL ID I SEE IN THE HORIZON RWI
}
};
my $response2 = $TPP_Client->send_cmd($request2);
my $success = $response2->{is_success};
my $first_name = $response2->{attributes}{first_name};
print "success is $success\n";
print "first_name is $first_name\n";
$success always returns 0....
Why doesn't this work? I also tested the update action for the contact
object and that did not seem to work either... This is all under Horizon,
anyone see any reason why this should not work? Unless these functions are
really (not yet available) in which case I would be quite upset that I
wasted my time trying to figure this out.
--
John Keegan
[EMAIL PROTECTED]
http://RackShare.com
> From: John Keegan <[EMAIL PROTECTED]>
> Date: Wed, 27 Nov 2002 17:52:10 -0500
> To: <[EMAIL PROTECTED]>
> Subject: Existing Users for Webcerts
>
> I am working with 2.60's reg_cert.cgi and it does not appear that an
> existing users information is pre-populated in the order form...
>
> Is this an error on my part or is this ability really not included?
