Bugzilla – Full Text Bug Listing
| Summary: | WSE support for basic-authenticating firewalls | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [WebTools] WTP Webservices | Reporter: | Chris Brealey <cbrealey> | ||||
| Component: | wst.ws | Assignee: | Andrew Mak <makandre> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | major | ||||||
| Priority: | P2 | CC: | gilberta, matt, pmoogk, sylvain.duguet, WURTHEMM | ||||
| Version: | 0.7 | ||||||
| Target Milestone: | 1.5.1 M151 | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Chris Brealey
*** Bug 102538 has been marked as a duplicate of this bug. *** Targetting M10. Deferring enhancements to WTP 1.5 per the memo "Achieving WTP 1.0 Quality Targets" by Arthur Ryman [1]. [1] http://dev.eclipse.org/mhonarc/lists/wtp-dev/msg02831.html changing target from 1.5 M1 to 1.5 M5 to reflect new numbering system as we join Collisto. Moving to M6. Getting a tad late in M5. Changed to a bug. This isn't so much an RFE as it is a deficiency in the WSE which at one time did support basic-auth / https. Request for an higher priority, like P1 (not enough rights to do that). Hoping to make this bug the most squeaky wheel and then get the grease ;-) *** Bug 142511 has been marked as a duplicate of this bug. *** Clearing Target Milestone field and using Whiteboard field to capture desired target: 1.5 RC4. RC4 is effectively closed. Changing outlook (status whiteboard) from 1.5 RC4 to 1.5 RC5. Back to using the target milestone field to indicate intended as well as actual target miletones/RCs. This bug is a candidate for 1.5 RC5. This will be fixed in the WTP 1.5.1 maintenance release. Sylvain, let me know if this interferes with your plans for adopting/using WTP's Web Services Explorer. Is this bug really a P1? P1 means release defining. Current code (at least 20060508 build) supports basic auth: when receiving a 401 status code from a webservice server, it opens a dialog box to get user login information and uses it in an Authorization header with Basic scheme. That looks fine for me on that point. *But* https tunneling is not handled as said in a comment above (2006-03-09 16:19). The TODO found in org.eclipse.wst.ws.internal.explorer.platform.wsdl.transport.HTTPTransport.buildSocket(), line 495 is the blocking one for our needs. For https with Proxy authentication (TODO at line 502), same remark applies. I'd summarize the situation saying that the missing SSL tunneling is blocking, is a P1 and is required for 1.5. Lowering priority. Chris had confirmation from Sylvain (through e-mail) that targetting this bug to 1.5.1 is OK. Andrew, please take a look at this for WTP 1.5.1. Regarding the TODO on line 495, the comments in bug 84945 indicated that a possible approach is to use Axis runtime as the transport manager. I have found that the following code will create a socket that will allow us to tunnel through the proxy: SocketFactory sf = SocketFactoryFactory.getFactory(HTTPS, new Hashtable()); s = sf.create(host, port, null, null); However, this only works when there is no basic authentication. When I put a TCP/IP monitor between the WSE and the proxy server, this is the request being sent: CONNECT castle.torolab.ibm.com:9443 HTTP/1.0 User-Agent: AxisClient Content-Length: 0 Pragma: no-cache Clearly, the Proxy-authorization header is missing, even though both https.proxyUserName and https.proxyPassword system properties are set. I discovered from this page (http://ws.apache.org/axis/java/client-side-axis.html#AxisProperties) that Axis uses http.proxyUser rather than http.proxyUserName. Setting the https.proxyUser property causes the Proxy-authorization header to be sent, however, the request still got rejected by the proxy server. Created attachment 48465 [details]
build socket for https tunneling
The second option was to build our own tunneling socket, which is what this patch is doing. Please give it a try.
Over to you Peter, thanks. This defect has been reviewed/committed/ and released under v200608231830. Verified on 1.5.1. Closed. |