Access gate
The access gate decides who may reach an application's web pages. The platform checks it at the edge, before a request reaches your own container. It applies to the services of the application that have a public route.
The gate is off by default. Everyone who knows the address can reach the application.
Opening the page
Open the application and select Access gate. Any member can read the page. Only an owner or admin of the organization can change it. Other members see a notice.
The four modes
| Mode | What a visitor sees |
|---|---|
| No gate | Nothing changes. The application answers as it did before. |
| HTTP Basic auth | The browser asks for the one username and password you set. |
| Shared token | The request needs a token. It gets a 401 response without one. |
| someones.computer sign-in | A signed-out visitor goes to the sign-in page, then back to the application. A signed-in visitor who isn't a member of the owning organization gets a 403 response. |
Basic auth
Choose the mode and enter a username and password. You need both. Saving again replaces the old password. The platform never shows the password again.
Shared token
Choose the mode and save. The platform shows the token once, under Token issued, copy it now. Send it with each request in one of two ways:
- The header
X-Someones-Gate-Token. - The query parameter
gate_token, for links that can't carry a header.
Saving with this mode always issues a new token. The old token stops working at once. This is how you rotate it. Nobody can read the token later.
Platform sign-in
The platform stores no credential. The check uses the same membership rule as the rest of the platform. After the visitor signs in, the platform sends them back to the page they asked for.
A running application needs a redeploy
The platform writes the gate into the routing labels of a revision when it places that revision. If the application is already running, saving shows a confirmation: the platform restarts it with the same code, so the new gate takes effect now. Nothing rebuilds. If you decline, the setting applies at the next deploy. A stopped application just picks the setting up when it next runs.
Wrong guesses slow down
Basic and token modes count wrong attempts from each source address. After 10 wrong attempts in
5 minutes, the gate answers 401 to that source, even for a right credential, until the window
passes. A right credential never uses up the limit.
Related
- Applications
- API tokens. These are for the platform's own API. They don't open a gate.