Manage a private connector

Verify the private route from the runtime to the approved target.

Before you start

Use a self-hosted deployment for private connectivity. Identify the connector owner, permitted network, and registered target.

Procedure

1. Inspect the connector state and its intended route context.

2. Check that the target registration uses the matching approved private route and credential mode.

3. Run connectivity checks from the runtime path, including name resolution and the permitted target endpoint.

4. After a connector or route change, verify accepted configuration and retry a harmless governed call.

Verify the result

Confirm upstream reachability through the connector and metadata-only audit for the request. A laptop connectivity test is insufficient.

If it does not work

An unavailable or disallowed private route must fail closed. Fix route state or registration instead of adding a broad address bypass.

Read the related concept or consult the Admin API for exact request fields.

Implementation reference

Read the source contract.