Open cbarga opened 2 years ago
Note: I did successfully login to the Conjur CLI using the customer's authn_login and API key.
I have a couple of other customers facing the same issue now. Can someone take a look?
This can be closed. I stood up my own TeamCity instance and followed the readme for this project and was successful, even with the non-standard port for conjurfollowers-qa. I will work with my users to ensure they have their connection setup correctly.
Summary
A clear and concise description of what the bug is.
My customer setup the plugin using the values from his existing PCF integration. e.g. account, applicance_url, authn_login, etc. He gets this error when setting up the plugin,
ERROR: Authenticating to conjur at 'https://conjurfollowers-qa..com:444' with account '' and with login 'host/pcf/pcf-np/d79fa6c3-5453-459f-a19b-c2d290a8a017/346334f5-4373-432b-8d53-bf3452c6fc4b'. Failed to authenticate. Received status code: 0
Note, we use port 444 because we had issues with the SSL config when setting up the followers. I can't remember the details, but Ben Floyd might remember.
Steps to Reproduce
Steps to reproduce the behavior:
Expected Results
For the pipeline to retrieve values from Conjur/DAP and inject them into the pipeline's env
Actual Results (including error logs, if applicable)
ERROR: Authenticating to conjur at 'https://conjurfollowers-qa..com:444' with account '' and with login 'host/pcf/pcf-np/d79fa6c3-5453-459f-a19b-c2d290a8a017/346334f5-4373-432b-8d53-bf3452c6fc4b'. Failed to authenticate. Received status code: 0
Reproducible
Version/Tag number
We are running v10.11 of DAP, which is functionally equivalent to 11.0 and only released to our org. TeamCity version is 2021.2.1 (build 99602)
Environment setup
Additional Information
It seems strange that the status code is 0, given that it's an error.