![]() I think that my only option left is to programmatically hook into the JAX-WS HTTPS configuration to setup the keystore and truststore for the client JAX-WS interaction.Īny ideas/pointers on how to do this? All information I find either uses the method or is setting the global SSLContext that -I guess- will end up in the same confilc. I also tried adding my client certificate into my original keystore, but -again- my other components don't seem to like it either. seemed to indicate separation, but it's not the case) ), it seems that they end up using the global SSLContext. ![]() Although my other components are using dedicated parameters for their SSL configuration ( my.xmpp.keystore=xxx, my.uststore=xxy. I tried adding a new keystore through the standard system configuration ( =xyz) but my other components are clearly affected by this. In this communication, my server acts as client in the JAX-WS interation and I've a client certificate signed by the 3rd party. Now I need to securely connect to a 3rd party server using JAX-WS over HTTPS/SSL. My server has a CA-signed certificate to let my clients connect using TLS (SSL) communication using HTTP/S and XMPP(secure). ![]() I'm working on a server in a distributed application that has browser clients and also participates in server-to-server communication with a 3rd party. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |