Community
Participate
Working Groups
Build ID: 2.0M5 Steps To Reproduce: We are using WebServicesExplorer as testing tool for web services. Works fine when using standard development environment, where we have access via HTTP to the server providing the web services. Within integration environments, and sometime for queries in production environment, the servers are only accessible via HTTPS and client-certificates. The current implementation of org.eclipse.wst.ws.internal.explorer.platform.wsdl.transport.HTTPTransport does support BasicAuth and proxies, but nothing for certificates. We would require: - configure a specific trust store (as server certificates are signed by a custom CA) - configure a specific keystore, where our client certificates can be stored. - Optionally configuring a hostname verifier, as we are accessing the server via SSH tunneling, so server-certificate does not match the current host (e.g. localhost). Verifier can be default, or one ignoring server name, or a contributed one. More information: I hope, this is not an obscure requirement, but related to specific infrastructure requirements in secure environments.
A good requirement, and not obscure at all. This requirement has been captured under RFE bug 154100 (see in particular bug 154100 comment 17) and reaches beyond the Web Services Explorer to any actual or conceivable plugin of the Eclipse platform that needs to open connections over HTTPS. Although it won't be covered in the first incarnation of the RFE in Eclipse 3.3, we will use RFE 154100 or an offshoot of it to track additional requirements against the Eclipse platform for managing internet / intranet connections. I suggest you add yourself to RFE 154100's CC list and add copy your requirements into a comment on the RFE. Thanks - CB. *** This bug has been marked as a duplicate of bug 154100 ***
Closing as part of mass query to clean up old resolved bugs in untargetted milestones.
