Hi, Thank you for the response :) So, the private key is not part of the issue, right? Wouldn't your private key only be used to decode a message sent from the web service to you? Per your message, that's not your issue.
Your saying the remote web service is rejecting the message you are sending, I assume you are using the public key of the web service to encode the message (you are sending)? Is that correct? Have you compared the xml sent from both clients (android and doNet). Is the result of that verification, the only difference is the "SignatureValue"? In other words, the xml structure from both clients are identical. Do you have a stack trace from the server that we can translate? I'm just trying to see if there are any more clues. What I've found is, different versions of the BouncyCastle library are incompatible. If you encode a value with an earlier version of BouncyCastle and then try to decode the value with a later version of BouncyCastle, an exception is raised. Do you have access to the source code of your "doNet" client. Can you see which library (and version) the other client is using and which algorithm (the algorithm should be published). Good Luck Jason -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to android-developers+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
