[
https://issues.apache.org/jira/browse/AXIS2-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477373
]
Oleg Kalnichevski commented on AXIS2-2274:
------------------------------------------
> In AbstractHttpSender, agent.getState().setCredentials(new AuthScope(host,
> port, realm), creds);
> When it's https, the port value here is 80, for example, contentvm2, 80,
> null. But because it's https, the Httpclient actually tries to connect to
> 443. So the response comes back as contentvm2, 443, null. That caused the
> getCredentials() to return null.
To me this looks like a configuration problem on your side (admittedly I know
very little about Axis2 configuration). You should be using contentvm2, 443,
null or contentvm2, -1, null as the correct auth scope for your credentials.
> Actually it's not exactly true. In Windows, if a domain user tries to
> authentication using Basic Auth, the domain name is required:
Yes, you are right. This is, however, a problem with HttpClient rather than
Axis2. Please consider opening a Jira ticket for this issue in HttpComponents
HttpClient. I am in the process of rewriting HTTP authentication code for
HttpClient 4.0 and will take this issue on board.
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
