Hi Guillaume,
Please see my comments in the mail.
tog wrote:
Hi Willem,
Can you explain in details your sentence: "The AuthorizationPolicy
only works for HTTP Conduit of HTTP Destination." as I am not familiar
with CXF internals.
CXF http transport is implemented by two component HTTP Conduit (client
side) and
HTTP Destination (server side).
But in the Service creation phase these two component are not involved ,
because CXF
just use the URL connection to get the WSDL file.
CXF delegate the WSDL creation to WSDL4J and it use the blow code to
create the WSDL
definition.
URL contextURL = (contextURI != null)
? StringUtils.getURL(null, contextURI)
: null;
URL url = StringUtils.getURL(contextURL, wsdlURI);
InputStream inputStream = StringUtils.getContentAsInputStream(url);
InputSource inputSource = new InputSource(inputStream);
inputSource.setSystemId(url.toString());
Document doc = getDocument(inputSource, url.toString());
I don't know if there is a way to set the basic authorization for the
url by using system properties.
In my case I am not using a proxy so the flag you are mentioning won't
help much. My server is waiting for the following http header:
"Authorization: Basic ..." and not "Proxy-Authorization"
OK, this is my mistake. I think you can write codes to get the WSDL from
the service which need use
HTTP basic authorization, and store this WSDL in the temp directory ,
then pass the temp WSDL file's URL
to the service.
I might need to dig a bit in order to see what is the effect on the
http request of setting the username and password of
AutorizationPolicy :-)
Cheers
Guillaume
Willem.
On Dec 9, 2007 9:32 PM, Willem2 <[EMAIL PROTECTED]> wrote:
Hi Guillaume
The AuthorizationPolicy only works for HTTP Conduit of HTTP Destination.
In your case , I don't think this policy will take effect, since CXF just
uses URL to get wsdl when create the service from wsdl.
Maybe you need to use JVM's proxy setting such as
-DproxySet=true -DproxyHost=PROXYSERVER -DproxyPort=PORT
Willem.
tog wrote:
Hum I can believe this ...
What I am looking for is a way to set up the Authorization header in
the HTTP request (prior to get the wsdl).
I know how to set-up the Proxy-Authorization header and I found
AuthorizationPolicy
AuthorizationPolicy auth = conduit.getAuthorization();
auth.setUserName(username);
auth.setPassword(password);
Will that do the job ?
Then the problem is to do this prior to the creation of the client ...
which is the first thing I do !
Any thought ?
Guillaume
On Dec 9, 2007 3:34 AM, Glen Mazza <[EMAIL PROTECTED]> wrote:
I'm not sure the Java artifacts would have a defined place for such
information.
Glen
Am Sonntag, den 09.12.2007, 01:15 +0800 schrieb tog:
the same question apply for the wsdl2java. I did not see anything for
setting up username/passwd in the options
On Dec 9, 2007 1:13 AM, tog <[EMAIL PROTECTED]> wrote:
Hi
I need basic auth to retrieve a wsdl.
I currently use the dynamic client. All the constructors take
directly
a string for the wsdl url.
Is there a way to set username/passwd before actually calling the
server ?
Thanks
--
Best Regards
Guillaume
http://cheztog.blogspot.com
--
Best Regards
Guillaume
http://cheztog.blogspot.com
--
View this message in context:
http://www.nabble.com/Dynamic-client---basic-auth-tp14230385p14238535.html
Sent from the cxf-user mailing list archive at Nabble.com.
