[JIRA] (JENKINS-16099) Not able to enter correct SVN credentials

[k...@kohsuke.org (JIRA)]

Kohsuke Kawaguchi commented on JENKINS-16099 Not able to enter correct SVN credentials I looked into this. I used BeanStalk free HTTP hosted Subversion repository to test this, but I failed to reproduce the problem. Here's what's supposed to happen when you step execute HttpConnection#_request (as of SVNKit 1.7.4-jenkins-3): http=BOGUS_AUTH (l.328) executes because ahtnetication is being forced (this is a SVNKit jargon of saying that we will send a credential without waiting for the server to reject us first — this is needed because some repository allows read-only anonymous access.) request.dispatch(method, path, header, ok1, ok2, context); (l.385) runs, resulting in the bogus authentication header sent to the server. myLastStatus = request.getStatus(); (l.402) runs, and the response code should be 401 (Unauthorized) myLastStatus.getCode() == HttpURLConnection.HTTP_UNAUTHORIZED (l.502) matches authManager.getFirstAuthentication(ISVNAuthenticationManager.PASSWORD, realm, myRepository.getLocation()); (l.598) executes and this is where we pick the actual credential entered by the user. continue; executes and the execution comes back to the top of while(true) (l.347) request.dispatch(method, path, header, ok1, ok2, context); (l.385) runs again, and it succeeds. Clearly, your code execution path is being different. Any chance you can step execute and tell us what you see?

This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira