You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2006/10/12 19:27:35 UTC
[jira] Resolved: (AXIS2-1040) Basic Authentication lock up
[ http://issues.apache.org/jira/browse/AXIS2-1040?page=all ]
Davanum Srinivas resolved AXIS2-1040.
-------------------------------------
Resolution: Fixed
Should be fixed in latest SVN. Please let us know if you still see the problem. you have complete control over the authentication process via options.
thanks,
dims
> Basic Authentication lock up
> ----------------------------
>
> Key: AXIS2-1040
> URL: http://issues.apache.org/jira/browse/AXIS2-1040
> Project: Apache Axis 2.0 (Axis2)
> Issue Type: Bug
> Affects Versions: 1.0
> Environment: Windows 2003 with Sharepoint Portal Server, configured to use IIS basic authentication.
> Reporter: jeff ling
>
> First, I can use browser (Firefox) connect and login to the site, so authentication on the server side doesn't have issue.
> But when I use Axis to do the same, I got into an infinite loop. The following messages are repeated over and over:
> 08-16@16:37:39 DEBUG [main] (StAXUtils.java:126) - XMLStreamWriter is com.ctc.wstx.sw.SimpleNsStreamWriter
> 08-16@16:37:39 DEBUG [main] (OMSourcedElementImpl.java:520) - serialize {http://microsoft.com/webservices/SharePointPortalServer/UserProfileService}GetUserProfileByIndex to XMLStreamWriter
> 08-16@16:37:39 DEBUG [main] (EntityEnclosingMethod.java:504) - Request body sent
> 08-16@16:37:39 DEBUG [main] (HttpMethodDirector.java:837) - Authorization required
> 08-16@16:37:39 DEBUG [main] (AuthChallengeProcessor.java:89) - Supported authentication schemes in the order of preference: [ntlm, digest, basic]
> 08-16@16:37:39 DEBUG [main] (AuthChallengeProcessor.java:110) - Challenge for ntlm authentication scheme not available
> 08-16@16:37:39 DEBUG [main] (AuthChallengeProcessor.java:110) - Challenge for digest authentication scheme not available
> 08-16@16:37:39 INFO [main] (AuthChallengeProcessor.java:100) - basic authentication scheme selected
> 08-16@16:37:39 DEBUG [main] (AuthChallengeProcessor.java:154) - Using authentication scheme: basic
> 08-16@16:37:39 DEBUG [main] (AuthChallengeProcessor.java:162) - Authorization challenge processed
> 08-16@16:37:39 DEBUG [main] (HttpMethodDirector.java:706) - Authentication scope: BASIC 'soto.corp.google.com'@soto.corp.google.com:2003
> 08-16@16:37:39 DEBUG [main] (HttpMethodDirector.java:855) - Credentials required
> 08-16@16:37:39 DEBUG [main] (HttpMethodDirector.java:869) - BASIC 'soto.corp.google.com'@soto.corp.google.com:2003 new credentials given
> 08-16@16:37:40 DEBUG [main] (HttpMethodDirector.java:193) - Retry authentication
> 08-16@16:37:40 DEBUG [main] (HttpMethodBase.java:921) - Resorting to protocol version default close connection policy
> 08-16@16:37:40 DEBUG [main] (HttpMethodBase.java:925) - Should NOT close connection, using HTTP/1.1
> 08-16@16:37:40 DEBUG [main] (HttpConnection.java:1175) - Connection is locked. Call to releaseConnection() ignored.
> 08-16@16:37:40 DEBUG [main] (HttpMethodDirector.java:277) - Authenticating with BASIC 'soto.corp.google.com'@soto.corp.google.com:2003
> 08-16@16:37:40 DEBUG [main] (HttpMethodParams.java:355) - Credential charset not configured, using HTTP element charset
> 08-16@16:37:40 DEBUG [main] (HttpMethodBase.java:1235) - Adding Host request header
> The same client works when connecting to another web site with basic authentication. So I am not sure what was the cause here.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org