Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I have a sword server which uses https and the swordclient fails basic authentication via TLS/SSL with message that no credentials are available.
The exact same POST via http succeeds.
Logged In: YES
Thanks for your comment. We've not tried running it this way. Have you been able to look at the code to see why this might be happening?
Logged In: NO
no, I have not looked at the code in depth. I use this sword client to verify interoperability of our sword server implementation with various clients, but I am not a java programmer.
Is the server you are connection to using a self-signed (or 'invalid' in one way or another) certificate? If so, I'm working on a fix for this.
yes the server is using a self-signed certificate.
Sorry for not mentioning this.