[HAP-736] Jenkins builds may fail due to 401 error when authenticating using the Credentials plugin Created: 05/May/16  Updated: 14/Nov/17  Resolved: 07/Jun/16

Status: Resolved
Project: Jenkins Artifactory Plug-in
Component/s: None
Affects Version/s: None
Fix Version/s: 2.5.0

Type: Bug Priority: Blocker
Reporter: Andrei Komarov Assignee: Alexei Vainshtein
Resolution: Fixed Votes: 2
Labels: None


When using the credentials plugin with Jenkins Artifactory plugin for running a Jenkins build job, it may fail due to "lost" credentials.

Server and plugin versions reproduced on:
Artifactory 4.7.1
Jenkins 1.603
JAP 2.4.7

Steps to reproduce:
1. Use the manage menu to define credentials for Artifactory
2. Configure a Maven job (tested with our Maven-Example) as well as the previously set credentials
3. Build successfully
4. Stop Jenkins (completely)
5. Start Jenkins
6. Run the job again; if anonymous deploy is disabled, the job will fail with 401 error.


Manually specify Artifactory credentials within a given build.

Generated at Wed Jun 03 03:31:04 UTC 2020 using Jira 8.5.3#805003-sha1:b4933e02eaff29a49114274fe59e1f99d9d963d7.