-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
1
-
Minor
-
Issue Summary
Invoking a Jenkins pipeline using a Compass template fails when passing basic authentication in the webhook URL. The URL works in Postman, but Compass encounters an error. Simplifying the test with "webhook.site" without authentication succeeds, but adding authentication causes Compass to fail. The error is confirmed to be due to the authentication in the URL, as tests without it work correctly.
Steps to Reproduce
- Create a Jenkins pipeline job that requires basic authentication.
- Successfully test the Jenkins pipeline invocation in Postman using the Jenkins API token.
- Attempt to create a Compass template that invokes the Jenkins pipeline, including basic authentication in the webhook URL.
- Observe the error when creating the template in Compass.
- Test the webhook invocation using a public DNS like "webhook.site" without authentication (should succeed).
- Test the webhook invocation with authentication using Postman (should succeed).
- Attempt to use the Compass template again with authentication (should fail).
Expected Results
The Compass template should successfully invoke the Jenkins pipeline with basic authentication included in the webhook URL.
Actual Results
The Compass template fails to invoke the Jenkins pipeline due to the basic authentication in the webhook URL, despite successful tests in Postman and using a public DNS without authentication.
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
- relates to
-
COMPASS-25 Support for Authentication and Custom Headers in Compass Templates
- Gathering Interest
Upon further review by the team, this capability of adding userInfo was not included in the original set of functionality. We are going to track this as a feature request rather than a bug, as the main functionality is not affected. We are going to track this internally as such.