|
||||||||
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... d...@fortysix.ch (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... d...@fortysix.ch (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... d...@fortysix.ch (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... ku...@gmx.de (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... d...@fortysix.ch (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... k...@kohsuke.org (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... d...@fortysix.ch (JIRA)
- [JIRA] (JENKINS-16099) Not able to enter corr... ku...@gmx.de (JIRA)
I'm not sure I'm the best man to look at it. I looked at the error description and I didn't understand what the problem is.
Why are you not able to configure the credentials? Is this authentication-forced not a workaround for a deeper lying problem?