[JIRA] [core] (JENKINS-32293) Configure proxy authentication scheme

[seme...@gmail.com (JIRA)]

Title: Message Title

Christian Effertz closed an issue as Won't Do   There is no need to configure it over the Jenkins UI. This can be configure via a system property. Have a read in the documentation: Controlling which authentication scheme is used When a server needs a client to authenticate, it may propose a number of schemes to the client (for example digest and ntlm) and the client may choose from among them. Normally, applications do not care which scheme is used to and the implementation automatically chooses the strongest (most secure) protocol transparently. If the user needs to ensure that a particular scheme is used, then the following system property can be set to modify the default behavior. -Dhttp.auth.preference="scheme" -D is specified if the property is being set on the command line. "http.auth.preference" is the property name, and scheme is the name of the scheme to use. If the server does not include this scheme in its list of proposed schemes, then the default choice is made. I did not find it either in the beginning Jenkins / JENKINS-32293 Configure proxy authentication scheme Change By: Christian Effertz Status: Open Closed Resolution: Won't Do Add Comment   This message was sent by Atlassian JIRA (v6.4.2#64017-sha1:e244265) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.