Authentification with Jenkins-Job is not working
Description
Environment
relates to
Activity
Thomas Soring July 18, 2013 at 11:51 AMEdited
Hi Mark,
this bug is solved. But I'm still getting this error in the log:
What is the function of /state and why is the authentication for this url still worng?
Thanks
Mark Rekveld July 17, 2013 at 1:25 PM
Hi Thomas,
The fix is only in the JIRA plugin so updating the Jenkins plugin is not required.
But the release will come with a new feature for Jenkins, The ChangelogAnnotator, so updating could be useful.
The new version will be available later tonight.
Thomas Soring July 17, 2013 at 1:22 PM
Hello Mark,
when will the new version be released?
Do i need to update the jenkins-plugin as well?
Thanks
Thomas
Mark Rekveld July 17, 2013 at 12:52 PM
In some cases the Basic authentication header was not added.
It looks like it was only being added if there was a user that directly or indirectly caused the action. But when the schedular was triggered the basic header was not added.
I corrected this and it should work now also for schedular triggered actions.
Hello there,
we authenticate our services with atlassian crowd. So Jira and Jenkins are connected to crowd.
We've installed both, the jira- and the jenkins-plugin in version 1.1.4.
The Configuration works fine using this guide:
https://moss-cave.atlassian.net/wiki/display/JJI/Advanced+Application+Links
But when synchronizing a job only this error is shown in the jenkins-log and the synchronisation is not working.
Don't know why using the localhost-address.
In both Systems every user must be logged in. When giving the anonymous user the read-permission, the jobs are synchronized.
We've configured the jenkins-admin for authentication, which has enough rights for the connection. But your plugin is using the anonymous-account.
At the outgoing-configuration-page we have also tested the API-Token and the normal password.
What can I do now? How do I know, why he is using the anonymous-Account?
Thanks for your help,
Thomas