Forum Discussion
15 years ago
Interesting question, I shall follows the results as i'm having the exact same problem.
I havn't found the solution (obviously), but I do get this same error (403.7) when I try to communicate from a simple Java class using javax.net.ssl package. I'm not really sure if its a java configuration problem when attempting to communicate with a windows based ssl / tls server or totally something else.
When I couldn't obtains results with my simple class, i've switched to do some test with SoapUI. I have been trying to execute exactly what you have described in your post, and I do get the same http error message.
Now, I have been browsing the web searching for a way to specify directly the 'Windows Certificate Registry' instead of a custom made keystore. I havn't found how, nor any trails that could hint at the possibility of doing this.
I wish for a solution, as I've been plagued by this ssl / tls communication problem between Java base application and a C# / .net application for the last month!
I havn't found the solution (obviously), but I do get this same error (403.7) when I try to communicate from a simple Java class using javax.net.ssl package. I'm not really sure if its a java configuration problem when attempting to communicate with a windows based ssl / tls server or totally something else.
When I couldn't obtains results with my simple class, i've switched to do some test with SoapUI. I have been trying to execute exactly what you have described in your post, and I do get the same http error message.
Now, I have been browsing the web searching for a way to specify directly the 'Windows Certificate Registry' instead of a custom made keystore. I havn't found how, nor any trails that could hint at the possibility of doing this.
I wish for a solution, as I've been plagued by this ssl / tls communication problem between Java base application and a C# / .net application for the last month!
Related Content
Recent Discussions
- 15 years ago