-
Suggestion
-
Resolution: Unresolved
-
None
-
2
-
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
-
- mentioned in
-
Page Failed to load
[COMPASS-25] Support for Authentication and Custom Headers in Compass Templates
Support reference count | New: 2 |
Remote Link | New: This issue links to "Page (Confluence)" [ 1003250 ] |
Summary | Original: Support for Basic Authentication in Compass Webhook URLs | New: Support for Authentication and Custom Headers in Compass Templates |
Description |
Original:
We request the development of a feature to support basic authentication in webhook URLs within Compass templates. This enhancement should allow Compass to successfully handle URLs that include basic authentication, enabling seamless integration with Jenkins pipelines and other services that require authentication.
|
New: 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. |
Assignee | New: Josh Campbell [ 05fa5aee2f02 ] |
Link |
New:
This issue is related to |