-
Suggestion
-
Resolution: Unresolved
-
None
We request a feature that allows Compass templates to support basic authentication, custom headers, and token-based methods like bearer tokens, OAuth, and API keys. This would let Compass handle URLs with different types of authentication, making it easier to securely connect with Jenkins pipelines and other services that need secure access. Adding these options would make Compass more versatile and useful for working with a range of secure systems.
- is related to
-
COMPASS-23 Error Invoking Jenkins Pipeline from Compass Template with Basic Authentication in URL
-
- Closed
-
Hi everyone, this would be very useful, and make sense. There is a quite interesting example explained in this article related to compass templates https://community.atlassian.com/t5/DevOps-articles/How-to-Compass-Templates/ba-p/2814556
We would like to run an aws lambda throught a webhook, but it isn´t sound secure doing it if you don´t have any authentication in front of the lambda.