<@U04S8PLJWMT> i get `certificate verify failed: s...
# replication-ask-aim
Mateo Colina
12/16/2025, 9:03 PM@kapa.ai i get
certificate verify failed: self signed certificate in certificate chaink
kapa.ai
12/16/2025, 9:04 PMAirbyte (including the Connector Builder) does not currently provide a built‑in way to: - upload or configure custom CA certificates per connector, or - globally disable/skip SSL verification for HTTP‑based connectors. This limitation appears across several connectors when dealing with self‑signed or private CA certificates (MongoDB/DocumentDB, Elasticsearch/OpenSearch, GitLab, Google Analytics behind zScaler, etc.), and the official responses consistently state that custom certificates are not supported and that you’d need to patch the connector image or trust store yourself if you want to work around it.[\[Self‑signed Mongo/ES\]](https://discuss.airbyte.io/t/983); [\[GitLab SSL error\]](https://discuss.airbyte.io/t/1526); [\[Elasticsearch private CA\]](https://discuss.airbyte.io/t/268); [\[Elasticsearch source private CA\]](https://github.com/airbytehq/airbyte/issues/49816); [\[Azure Table local / self‑signed\]](https://github.com/airbytehq/airbyte/issues/58097) So, for your specific situation with Connector Builder: - There is no documented, supported toggle to “ignore SSL verification” for a Connector Builder HTTP request. - There is no documented way to inject your self‑signed CA into the Connector Builder’s trust store via the UI or standard configuration. Workarounds that have been suggested in similar cases involve customizing the underlying Docker image (e.g., adding your CA to the container’s trust store or patching the connector code), but these are not documented as official steps for the Connector Builder specifically and would require you to maintain a custom image.[\[Self‑signed Mongo/ES\]](https://discuss.airbyte.io/t/983); [\[GitLab SSL error\]](https://discuss.airbyte.io/t/1526) Because the knowledge sources do not include a Connector‑Builder‑specific solution, the most accurate guidance is: - Use a certificate signed by a trusted CA (or have your corporate CA installed at the Docker/host level so the container inherits trust), or - Build and run a custom Airbyte/Connector‑Builder image with your CA added to the trust store (unsupported but mentioned as the only current workaround for similar SSL issues). If you need an officially supported way to handle self‑signed certs in the Connector Builder, you’d need to open or upvote a GitHub issue so the team can prioritize adding custom CA / SSL configuration for builder‑based connectors.[\[GitLab SSL error\]](https://discuss.airbyte.io/t/1526); [\[Elasticsearch private CA\]](https://github.com/airbytehq/airbyte/issues/49816)
m
Mateo Colina
12/16/2025, 9:30 PM@kapa.ai is there a way to create a connector with connector builder by providing an openapi spec?
k
kapa.ai
12/16/2025, 9:30 PMA message from kapa.ai
kapa.ai
12/16/2025, 9:31 PMYes. The AI Assistant in Connector Builder can use an OpenAPI specification to help you create a connector: - You start in Connector Builder (new or existing connector) and click the “AI Assist” button. - Provide your OpenAPI specification URL (or a link to the API docs). - The Assistant analyzes it and auto‑configures things like base URL, authentication, pagination, request options, stream metadata, and stream configurations. [[AI Assist overview](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/ai-assist#how-it-works); [Getting started](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/ai-assist#getting-started)] You then review and refine the generated configuration as needed; it’s not fully automatic, but it significantly accelerates building a connector from an OpenAPI spec.
m
Mateo Colina
12/16/2025, 9:35 PM@kapa.ai i don't have access to AI Assistant
k
kapa.ai
12/16/2025, 9:35 PMA message from kapa.ai
kapa.ai
12/16/2025, 9:35 PMWithout access to the AI Assistant, there is no documented way to directly import an OpenAPI spec into the Connector Builder and have it auto‑generate the connector for you. The OpenAPI‑driven flow is specifically described as a capability of the AI Assistant, where you provide either a link to the API documentation or an OpenAPI spec URL and it analyzes and configures the connector (endpoints, auth, pagination, streams, etc.). [[AI Assist how it works (Next)](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/ai-assist#how-it-works); [AI Assist overview](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/ai-assist)] Without that feature enabled, you’d need to: - Create a Connector Builder project manually (“Start from scratch” / “Skip and start manually”). [[Connector Builder tutorial](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/tutorial#step-2-initial-configuration)] - Configure inputs, authentication, and streams yourself (API endpoint URL, headers, etc.), effectively translating the OpenAPI spec by hand into the Builder configuration. [[Connector Builder tutorial](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/tutorial#step-2-initial-configuration)] The knowledge sources do not mention any alternative, non‑AI‑Assistant import path for OpenAPI specs.
8 Views