Add support for self-signed certificates

Feature Requests
1

[Feature Request] Add support for self-signed certificates in GitLab connector and other services

Problem Description

Currently, the GitLab connector (and potentially other service connectors) doesn’t properly support self-signed certificates, which creates difficulties when working with:

  • Internal GitLab instances
  • Development/staging environments
  • Air-gapped networks
  • Organizations with strict security policies requiring internal CAs

This results in SSL/TLS handshake failures and prevents integration with these services.

Expected Behavior

The connector should:

  1. Allow configuration to trust specific self-signed certificates
  2. Provide an option to disable certificate verification (for development purposes only)
  3. Support custom CA certificates
  4. Maintain clear warnings about security implications when bypassing verification

Proposed Solution

  1. Add configuration parameters for:

    • allow_self_signed (boolean)
    • ca_cert_path (string path to custom CA bundle)
    • skip_ssl_verification (boolean, with appropriate warnings)

  2. Implement proper certificate handling in the underlying HTTP client

Additional Context

This is particularly important for:

  • Enterprise users with internal CA infrastructure
  • Developers testing integrations before deploying to production
  • Educational environments where public certificates may not be available