Components and installation
What the components are, where they come from, and how to install Gate One with the optional services.
Start with the feature that matches your need. Each page says why you would use it, shows a short configuration and links to the generated reference.
The components, where they come from, and how to install Gate One with the optional services.
The reverse proxy, cladone-auth,
auth-bridge, the token broker and Redis, one page each.
SSO, multiple identity providers, APIs and MCP, injectable UX, delegated credentials, usage events.
Copyable, schema-validated configurations for each feature.
Task-oriented deep dives: strict CSP and declarative UI gating.
Who authorizes, who identifies, and which
authProvider.type to use.
Request path, provider types, HA and the plugin boundary.
Write, sign and publish out-of-process extensions.
Every field, generated from the published JSON Schemas.
The source repository is generic Git hosting (GitHub, GitLab, Bitbucket
or self-hosted). Gate One is source-available under BSL-CUSTOM: the
English LICENSE is authoritative, LICENSE.fr.md is a French
reference. Extension plugins may be closed-source/commercial under the
plugin exception.
What the components are, where they come from, and how to install Gate One with the optional services.
The services that make up a complete Gate One deployment, and how they fit together.
Who authorizes, who identifies, and which authProvider type Gate One uses.
How Gate One sits between the browser, the identity provider, the applications and the plugins.
Offline signed licences, one token per period, and how the gateway checks the hosts it serves.
Copyable, schema-validated configurations, some runnable on your machine.
Task-oriented deep dives that do not fit a single feature page.
Build and trust out-of-process extensions, and publish them for other operators.
Every field, generated from the published JSON Schemas.