|
||||||||
|
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)

I think you are right, the forcing of the authentication is a workaround for a deeper issue (which I don't really know), but we don't have this origin issue - but this workaround is an issue and does prevent us from updating the credentials via UI.
Without this workaround everything would work great for us, but maybe not for others - therefore I'll leave the original behavior as it is, but add the option to disable the workaround on request.
who else do you think should take a look?