Follow a request to GitLab
Your application needs the first 20 issues from acme/website. It calls a remote Connectors host, which reaches GitLab through an adapter. What travels between them, and who checks access?
Follow the request and its answer. Start with configured access, which is federation behaviour available today, then explore how the specified architecture adds user authorization, which has no runtime yet. Both are illustrated journeys with fictional data: a Rust/WASM module supplies their deterministic steps, and no real service is contacted.
Two services shown together; they can be deployed separately.
Loading the walkthrough…
What is configured before this call?
An operator configures the gateway route and downstream service credential, the adapter’s permitted project and GitLab origin, and the provider credential. The client has a separate gateway credential. The gateway has already loaded the downstream description; a caller’s describe request does not create a route.
Remote service traffic needs the intended verified TLS boundaries. The walkthrough uses no real credentials and makes no provider requests.
For a closer look at individual rules, explore the advanced contract exercises. To run an actual service, follow Getting started.