|
||||||||
|
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 |
||||||||
- [JIRA] (JENKINS-16099) Not able to enter correct S... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... [email protected] (JIRA)

No, that's not what I meant, but obviously I couldn't explain it right. So I try again:
It looks to me that your proposed change (the ability to disable authenticationForced) is a workaround for the real problem (that you cannot enter the correct credentials).
But that's just from my naive understanding of the issue.