wsimport can't authenticate · Issue #231 · javaee/metro-jax-ws (original) (raw)

This repository was archived by the owner on Feb 5, 2019. It is now read-only.

Description

Standard java.net.Authenticator can be used in client application to access
service URL protected via web.xml, or in a client application behind password-
protected firewall. However, the same can't be done to generate client
artifacts using wsimport. Wsimport doesn't have any options to specify Network
username/password. This is in contrast to AXIS, where artifact generation and
deployment tools have options to speciify network username/password.
Example 1: JAX-WS service is deployed under Tomcat 5.5 with security
constraints set for the service URL pattern for GET and POST. Wsimport is
unusable in this case.
Example 2: JAX-WS service is deployed outside of the intranet firewall.
Wsimport is unusable from inside of the firewall to generate client artifacts
even with -httpproxy option specified, because here is no way to provide
authorization information.

Environment

Operating System: All
Platform: All

Affected Versions

[JAXWS 2.0_2]