[MOBY-dev] BioMOBY ping

Paul Gordon gordonp at ucalgary.ca
Wed Nov 8 14:56:02 UTC 2006


It;'s not an immediate solution, but I would suggest to that people 
providing public SSL services get a real certificate if they can rustle 
up the money (only about $100/year).  I know most MOBY clients won't 
connect to unauthenticated services either, so making it really signed 
by an authority will make it so much more useful...
> Hi Pieter, 
>
>   
>> I'm having a problem with the BioMOBY ping thing. As far as I 
>> know the services I had registered in the central BioMOBY 
>> Central respond correctly to a BioMOBY ping request. They are 
>> listed as dead though on the BioMOBY website and I'm 
>> wondering why. The current suspects are:
>>
>> * Base64 encoded output. Does the agent decode base64 content 
>> correctly?
>> * HTTPS. My services require an https connection. If the 
>> agent is using Perl code it will probably complain about not 
>> being able to validate the certificate, but execute anyway. 
>> If the agent was written in Java it will refuse to execute 
>> the service if the SSL certificates can not be validated. Our 
>> certificates are self-signed, so you'd have to add them to 
>> your keystore to be able to execute our services with a Java client.
>>
>>     
> I bet that its listed as dead because of authentication. What can I do to get
> around this?
>
> Thanks,
>
> Eddie
>
>
>
> _______________________________________________
> MOBY-dev mailing list
> MOBY-dev at lists.open-bio.org
> http://lists.open-bio.org/mailman/listinfo/moby-dev
>
>
>   




More information about the MOBY-dev mailing list