>>What do you mean by 'custom' - just that it was not issued by a TTP ?
>
>Yes, it seems like it. Its a string they created and this is why it cannot be authenticated against the server. They are validating it in their own code. Thus, in the SOAP envelope they return, they send the proper message. For now, I keep receiving authentication failed.
>
>>Best ask whoever supplied the certificate. Can you post the string (I assume it's just the public key)
>
>Other than to post it as a parameter, which is not supported in that method, I do not know any other way to send a certificate. If it is not a certificate which validates against the server, I wonder if using X509 will work.

I meant can you post the string here on UT (or email it)