axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Oleg Kalnichevski (JIRA)" <j...@apache.org>
Subject [jira] Commented: (AXIS2-2274) Axis 2 as a client, access https:// doesn't work
Date Fri, 02 Mar 2007 10:15:51 GMT

    [ https://issues.apache.org/jira/browse/AXIS2-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477243
] 

Oleg Kalnichevski commented on AXIS2-2274:
------------------------------------------

Jeff,

I personally see no problem with the credential handling code as far as HttpClient is concerned.
 NTCredentials is a subclass of UsernamePasswordCredentials. Therefore it can be used with
Basic and Digest auth schemes. The domain and host attributes will simply have no effect.


Besides, HTTP authentication has no relation with HTTPS of what so ever. What specifically
does not work in your case? Can you produce a wire/context log of an HTTP session that exhibits
the problem or the exception stack trace at the very least? 

http://jakarta.apache.org/commons/httpclient/logging.html 

Oleg

> Axis 2 as a client, access https:// doesn't work
> ------------------------------------------------
>
>                 Key: AXIS2-2274
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2274
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1
>            Reporter: jeff ling
>         Assigned To: Saminda Wishwajith Abeyruwan
>            Priority: Critical
>
> When the server is IIS, https doesn't work. https itself is supported through Httpclient.
>                     The credential is put in to "state" as:
>                        agent.getState().setCredentials(new AuthScope(host, port, realm),
creds);
>                     The problem is that if it's https, real port is implied, and the
"port" here is the default "80". However, when the response comes back, the actually port
(usually 433) is returned. That caused the credential (provider) not found. 
> This is only one of the issues. The credential handling code below is really wrong:
>                 if (host != null) {
>                     if (domain != null) {
>                         /*Credentials for NTLM Authentication*/
>                         creds = new NTCredentials(username, password, host, domain);
>                     } else {
>                         /*Credentials for Digest and Basic Authentication*/
>                         creds = new UsernamePasswordCredentials(username, password);
>                     }
>                     agent.getState().setCredentials(new AuthScope(host, port, realm),
creds);
>                 } else {
>                     /*Credentials only for Digest and Basic Authentication*/
>                     creds = new UsernamePasswordCredentials(username, password);
>                     agent.getState().setCredentials(new AuthScope(AuthScope.ANY), creds);
>                 }
> First,  whether it's basic or Digest is not decided by whether domain name exists, and
realm applies to basic and digest, not integrated. If you look at the IIS web server config
screen, you will see. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


Mime
View raw message