feat: Add SSL certificate bypass support for self-hosted Confluence instances #4219
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Relevant Issues
resolves #4217
What is in this change?
This PR adds SSL certificate bypass support for self-hosted Confluence instances. Users can now enable a checkbox to bypass SSL certificate validation when connecting to self-hosted Confluence instances with self-signed certificates.
Key Changes:
bypassSSL
parameter throughout the Confluence connector systemConfluencePagesLoader
that setsNODE_TLS_REJECT_UNAUTHORIZED='0'
when enabledFiles Modified:
collector/utils/extensions/Confluence/ConfluenceLoader/index.js
- Core SSL bypass logiccollector/utils/extensions/Confluence/index.js
- Parameter passing and chunk source generationfrontend/src/models/dataConnector.js
- API integrationfrontend/src/components/Modals/ManageWorkspace/DataConnectors/Connectors/Confluence/index.jsx
- UI implementationfrontend/src/locales/en/common.js
- Translationscollector/extensions/resync/index.js
- Resync supportAdditional Information
This feature addresses the common issue where self-hosted Confluence instances use self-signed SSL certificates that cause connection failures. The implementation properly manages the
NODE_TLS_REJECT_UNAUTHORIZED
environment variable, setting it to '0' during requests and resetting it to '1' afterward to maintain security for other connections.