-
Bug
-
Resolution: Fixed
-
Medium
-
6.8.1
-
1
-
Severity 3 - Minor
-
Issue Summary
If one Docker tasks configured with "Use the agent's native credentials" and another with a specific credential, the second Docker task will overwrite the default config.json file causing the first Docker task to fail with authentication error
Steps to Reproduce
- Create two plans
- The first plan have a Docker task with "Use the agent's native credentials"
- The second plan have a Docker task with username and password, or shared credential
- Run the first plan
It run successfully with the default credential configured in the machine config.json - Run the second plan
The second plan run successfully with a different credential - Run the first plan again
Expected Results
- The first plan will run successfully again
- The second plan should run Docker command with --config option to store the credential in another file
Actual Results
The first plan fail with authentication error
Notes
The second plan Docker task credential have overwrite the default credential stored in ~/config.json file causing the first plan to use the credential that only works in second plan
Workaround
Avoid using Docker task in second plan. Replace it with Script task to use --config option