Maple Harness home

Maple Harness 2.6.2 released! What's new in 2.6.2

Single userTeams & hubs

One person, one machine: the agent, the proxy and your own usage.

Several people, from one shared proxy up to a hub of hubs.

How developers sign in #

On this page
  1. In plain words
  2. Step by step, with pictures
    1. 1. The admin turns developer sign-in on
    2. 2. Your first visit
    3. 3. When an admin must accept you first
    4. 4. Make a token
    5. 5. Sign your laptop's proxy in
    6. 6. Afterwards: see it, revoke it
    7. 7. When a sign-in is refused
  3. A token from an admin
  4. Signing in with your company account
  5. Sign your own proxy in
  6. Advanced: a token for CI and containers
  7. What admins see
  8. Expiry, renewal and revoking
  9. Limits

A developer on a shared proxy needs a token and a few lines that point their tools at the proxy. There are two ways to get them: a token from an admin (works everywhere, no extra setup), or signing in with the company account through the proxy's single sign-on address (the developer makes their own tokens). Both can run side by side.

Contents

In plain words #

  • Your admin can give you a token. They make it on the setup page's People & teams tab, copy it to you once, with the lines to paste into your tools. Nothing else to set up. With Maple on your laptop, you paste it on your own proxy's Hubs & chaining tab: your proxy joins the hub as you, and Maple Harness keeps using your proxy as always.
  • Or you sign in yourself. If your admin turned on developer sign-in, open the address they give you (such as https://maple-admin.example.com), sign in with your work account, and you land on My access: your own page, where you make tokens, see your usage, and copy the lines for your tools.
  • Your own Maple proxy signs in for you. On your laptop, Maple Harness talks to its own proxy, and that proxy signs in to the team hub with your company account: on its setup page (Hubs & chaining, Sign in with your company account), or in a terminal. It shows a link and a code, you type the code on My access, and your proxy is connected. It keeps itself signed in for a week, then asks you to sign in again.
  • With Maple Harness, one command: maple-harness proxy connect --sso https://maple-admin.example.com has your local proxy sign in. The harness keeps using your local proxy, which now reaches the hub's models.
  • Tokens you make yourself expire (after 30 days by default). Tokens from an admin do not, unless they chose a date.

Step by step, with pictures #

The whole sign-in as a developer sees it, from the first visit to a revoked laptop. The pictures come from a demo setup: a hub called acme-hub whose sign-in address is https://sso.acme.example:12464, ben's laptop proxy ben-laptop, and a stand-in identity provider in place of your company's. Your company's sign-in screen looks like your company's; the names, addresses, codes and dates are examples. The details of each step are in the sections below.

1. The admin turns developer sign-in on #

In plain words: nothing below works until an admin says who may sign in and whether they are let in at once.

On the setup page, Single sign-on, step 6. Developers (optional): Developer sign-in is Automatic (people in the listed domains or groups are added at their first sign-in) or Ask an admin (a first sign-in waits until an admin accepts it). The whole step: Single sign-on, Developer sign-in.

Step 6 of the single sign-on wizard, Developers (optional): developers who are not admins can sign in too and land on My access, a page of their own; the Developer sign-in choice set to Ask an admin, with its help below: a developer's first sign-in files a request; you accept it on People and teams.Step 6 of the single sign-on wizard, Developers (optional): developers who are not admins can sign in too and land on My access, a page of their own; the Developer sign-in choice set to Ask an admin, with its help below: a developer's first sign-in files a request; you accept it on People and teams.
The admin's choice: let developers in at once, or ask first. A demo setup.

2. Your first visit #

In plain words: open the address your admin gave you, sign in the way you sign in at work, and you land on your own page, My access.

The address shows one button, Sign in with your company's name. It is the same page admins sign in on, and it says so: admins manage the proxy there, developers get their own access there:

The hub's sign-in page: Sign in to acme-hub, Admins manage this proxy here; developers get their own access here, and the button Sign in with Acme.The hub's sign-in page: Sign in to acme-hub, Admins manage this proxy here; developers get their own access here, and the button Sign in with Acme.
The hub's sign-in address. A demo setup.

It takes you to your company's sign-in screen (here the demo's stand-in, which says so across the top):

The demo's stand-in identity provider, under a banner saying it is a stand-in used for the documentation and not a real sign-in service: ACME, Sign in to continue to Maple Harness (maple-acme), the work email ben@acme.example typed in, and Continue.The demo's stand-in identity provider, under a banner saying it is a stand-in used for the documentation and not a real sign-in service: ACME, Sign in to continue to Maple Harness (maple-acme), the work email ben@acme.example typed in, and Continue.
Your company's sign-in, played here by a stand-in.

Then you are back on the hub, on My access, signed in as you (with Automatic, you were added as a person just now, with the team your groups give you):

My access right after the first sign-in: signed in as ben@acme.example, person ben (team backend), with Sign out; Connect your tools, first the commands that sign your own Maple proxy in, then Maple Harness with a token, Claude Code and any OpenAI-compatible tool, each with Copy.My access right after the first sign-in: signed in as ben@acme.example, person ben (team backend), with Sign out; Connect your tools, first the commands that sign your own Maple proxy in, then Maple Harness with a token, Claude Code and any OpenAI-compatible tool, each with Copy.
My access on the first visit. A demo setup.

3. When an admin must accept you first #

In plain words: with Ask an admin, your first sign-in only sends a request. Wait for an admin, then sign in again.

At phone width: Request sent, Your request to use this proxy was sent to its admins. You can sign in again once an admin accepts it. With Back to the sign-in page.At phone width: Request sent, Your request to use this proxy was sent to its admins. You can sign in again once an admin accepts it. With Back to the sign-in page.
What a developer (cara, in the demo) sees while she waits.

The admin sees the request on People & teams, under Asked to use this proxy, and presses Accept (as a new person, with the team her groups suggest): the picture is under What admins see. When cara signs in again, she lands on My access:

My access after the admin accepted: signed in as cara@acme.example, person cara (team design), with the lines for her tools.My access after the admin accepted: signed in as cara@acme.example, person cara (team design), with the lines for her tools.
Accepted: the same page, now hers. A demo setup.

4. Make a token #

In plain words: under Make a token, say what it is for, press Make a token, then Copy. It is shown once: paste it where it goes before you leave the page.

At phone width: Your tokens, tokens made here stop working after 30 days, you may hold 5 at once; No tokens yet; Make a token, For: ben laptop.At phone width: Your tokens, tokens made here stop working after 30 days, you may hold 5 at once; No tokens yet; Make a token, For: ben laptop.
Name the token, then Make a token.
At phone width: the token ben laptop in the list, and the box Token ben laptop, Copy it now: you will not see it again, with the start of the token in a field, the button Copied, and I have copied it.At phone width: the token ben laptop in the list, and the box Token ben laptop, Copy it now: you will not see it again, with the start of the token in a field, the button Copied, and I have copied it.
Shown once: Copy takes the whole token (a narrow screen shows only its start).

5. Sign your laptop's proxy in #

In plain words: run one command on your laptop, open the link it prints (a phone works), type the code, check the proxy's name, and confirm. Your proxy then reaches the hub as you, and keeps itself signed in for a week.

In a terminal on the laptop (the setup page's Sign in with your company account does the same):

A terminal: maple-proxy chain connect --sso https://sso.acme.example:12464 prints the link https://sso.acme.example:12464/sso/access and a code, says the hub's page names this proxy and until when the code works, then, after the approval: signed in as ben@acme.example (person ben), the hub added as provider hub, its models reached as hub/model, and the date until which the running proxy renews the token by itself.A terminal: maple-proxy chain connect --sso https://sso.acme.example:12464 prints the link https://sso.acme.example:12464/sso/access and a code, says the hub's page names this proxy and until when the code works, then, after the approval: signed in as ben@acme.example (person ben), the hub added as provider hub, its models reached as hub/model, and the date until which the running proxy renews the token by itself.
The command, its link and code, then the sign-in.

On My access, under Connect your proxy: type the code, Check the code, read which proxy asked, then Yes, connect it (only if it is the proxy you just used). On a phone it looks like this; the same card on a computer is under Sign your own proxy in:

At phone width: Connect your proxy, a code typed in, Check the code, and the question: A Maple proxy named ben-laptop asked just now from 127.0.0.1. That is the address this browser uses. Is this your own proxy? Everything it sends here counts as you. Buttons Yes, connect it and No, refuse it.At phone width: Connect your proxy, a code typed in, Check the code, and the question: A Maple proxy named ben-laptop asked just now from 127.0.0.1. That is the address this browser uses. Is this your own proxy? Everything it sends here counts as you. Buttons Yes, connect it and No, refuse it.
Check the name before you confirm. A demo setup (each sign-in gets its own code).

The laptop proxy's setup page shows the same sign-in on Hubs & chaining, whichever way it was started:

Hubs and chaining on ben's laptop proxy, Sign in with your company account: signed in, hub: signed in to sso.acme.example:12464 as ben@acme.example (person ben), renews until a date a week later, with Sign in again and Disconnect, then the form for another sign-in.Hubs and chaining on ben's laptop proxy, Sign in with your company account: signed in, hub: signed in to sso.acme.example:12464 as ben@acme.example (person ben), renews until a date a week later, with Sign in again and Disconnect, then the form for another sign-in.
Signed in, and until when it renews itself.

With Maple Harness, one command has the local proxy do all of this (the harness keeps using its local proxy):

A terminal: maple-harness proxy connect --sso https://sso.acme.example:12464 says the local proxy is signing in, prints the link and a code, then: your local proxy is now signed in as ben@acme.example and the harness keeps using your local proxy; the hub's models are reached as hub/model, counted at the hub as you, renewed by the proxy until a date a week later.A terminal: maple-harness proxy connect --sso https://sso.acme.example:12464 says the local proxy is signing in, prints the link and a code, then: your local proxy is now signed in as ben@acme.example and the harness keeps using your local proxy; the hub's models are reached as hub/model, counted at the hub as you, renewed by the proxy until a date a week later.
The Maple Harness shortcut.

6. Afterwards: see it, revoke it #

In plain words: My access lists your proxy as your proxy (renews itself). Revoke cuts it off at once; the laptop then asks you to sign in again.

Your tokens on My access: ben-laptop, made by your proxy (renews itself), expires the next day (renews until a week later), last used a minute ago, with Revoke; ben laptop, made by you, here, expires in 30 days, not used yet, with Rotate and Revoke.Your tokens on My access: ben-laptop, made by your proxy (renews itself), expires the next day (renews until a week later), last used a minute ago, with Revoke; ben laptop, made by you, here, expires in 30 days, not used yet, with Rotate and Revoke.
Your proxy's token next to the one you made.

After Revoke, the laptop proxy's next request to the hub is refused, and its Hubs & chaining tab says so:

The laptop proxy's Hubs and chaining tab: needs attention, signed in to sso.acme.example:12464 as ben@acme.example (person ben), but the hub ended this sign-in (revoked there, or your access to the hub changed); Sign in again, on this page or with maple-proxy chain connect --sso; the buttons Sign in again and Disconnect.The laptop proxy's Hubs and chaining tab: needs attention, signed in to sso.acme.example:12464 as ben@acme.example (person ben), but the hub ended this sign-in (revoked there, or your access to the hub changed); Sign in again, on this page or with maple-proxy chain connect --sso; the buttons Sign in again and Disconnect.
Revoked at the hub: sign in again, or disconnect.

In a terminal on the laptop, maple-proxy chain status says the same:

A terminal, 80 columns: maple-proxy chain status. This proxy: ben-laptop. Hubs above: hub, its address, answers yes (401), note REVOKED: sign in again. Sign-ins with a company account: hub: REVOKED: sign in again, signed in to sso.acme.example:12464 as ben@acme.example (person ben), but the hub ended this sign-in; sign in again on the setup page or with maple-proxy chain connect --sso.A terminal, 80 columns: maple-proxy chain status. This proxy: ben-laptop. Hubs above: hub, its address, answers yes (401), note REVOKED: sign in again. Sign-ins with a company account: hub: REVOKED: sign in again, signed in to sso.acme.example:12464 as ben@acme.example (person ben), but the hub ended this sign-in; sign in again on the setup page or with maple-proxy chain connect --sso.
The same revocation, from the terminal.

7. When a sign-in is refused #

In plain words: if your account is not one the admin allowed (another domain, a group not on the list), the hub says so and nothing is made for you. Ask the admin.

Not allowed: sam@contractor.example is not allowed to sign in here. Ask an admin of this proxy to add your company account or domain. With Back to the sign-in page.Not allowed: sam@contractor.example is not allowed to sign in here. Ask an admin of this proxy to add your company account or domain. With Back to the sign-in page.
An account outside the developers' domains. A demo setup.

The admin sees it under Refused sign-ins on People & teams (What admins see).

A token from an admin #

On the setup page, People & teams, open the person's Access and tokens:

  • Make a token: what it is for (their laptop, CI), and when it expires (never, by default, or 7, 30 or 90 days, or a year). It has the proxy scope only and is tied to the person at once, so their budget, models and accounts apply from the first request. It is shown once, with Copy, together with the lines below.
  • How they connect: the same lines again later, without the token.
  • The list of their tokens: what each is for, who made it (an admin, the developer themselves, or their proxy (renews itself) for a proxy they signed in), when, when it expires and when it was last used, with Revoke, and Revoke all of the person's tokens.
People & teams with two people open: ana's tokens come from an admin, an ana laptop token that expires 2026-11-11 and was last used just now; ben signs in with single sign-on at id.acme.example as ben@acme.example, with a token made by their proxy (renews itself) and a token he made himself. Each has New token, How they connect and Revoke all.People & teams with two people open: ana's tokens come from an admin, an ana laptop token that expires 2026-11-11 and was last used just now; ben signs in with single sign-on at id.acme.example as ben@acme.example, with a token made by their proxy (renews itself) and a token he made himself. Each has New token, How they connect and Revoke all.
People & teams: how each person signs in, and their tokens. A demo setup.

The lines they paste (the proxy's address comes from its host names, or from the single sign-on settings). The first one is the normal way: the developer's own Maple proxy, on their laptop, joins this one with the token, and Maple Harness keeps using that local proxy as always.

# Their own Maple proxy: paste this token on its Hubs & chaining tab
On that proxy's setup page: Hubs & chaining, Connect this proxy to a parent hub.
  Address: https://maple.example.com:11535/v1
  Token:   <their token>
Test the connection then says who the hub counts it as.

Maple Harness keeps using that local proxy, as always.

# Advanced: Maple Harness without a proxy of its own (CI, containers; asks for the token)
maple-harness proxy connect https://maple.example.com:11535

# Claude Code
export ANTHROPIC_BASE_URL=https://maple.example.com:11537
export ANTHROPIC_API_KEY=<their token>

# OpenCode, or any OpenAI-compatible tool
#   base URL: https://maple.example.com:11535/v1
#   API key:  <their token>
How they connect, without single sign-on: first, Their own Maple proxy: paste this token on its Hubs and chaining tab, with the steps (Hubs and chaining, Connect this proxy to a parent hub, the address ending in /v1, their token; Test the connection then says who the hub counts it as; Maple Harness keeps using that local proxy, as always); then Advanced: Maple Harness without a proxy of its own (CI, containers; asks for the token); then Claude Code and OpenCode, each with Copy.How they connect, without single sign-on: first, Their own Maple proxy: paste this token on its Hubs and chaining tab, with the steps (Hubs and chaining, Connect this proxy to a parent hub, the address ending in /v1, their token; Test the connection then says who the hub counts it as; Maple Harness keeps using that local proxy, as always); then Advanced: Maple Harness without a proxy of its own (CI, containers; asks for the token); then Claude Code and OpenCode, each with Copy.
How they connect, on a hub without single sign-on: their own proxy first. A demo setup.

With developer sign-in on, the lines start with signing in instead: maple-proxy chain connect --sso <address> (or maple-harness proxy connect --sso <address>), which has the developer's own proxy sign in with their company account (Sign your own proxy in); pasting the token on their proxy comes second, then the advanced line.

How they connect, with single sign-on on: first, Their own Maple proxy: sign in with their company account, with maple-proxy chain connect --sso and the hub's sign-in address, or maple-harness proxy connect --sso, and the note that Maple Harness keeps using that local proxy; second, Their own Maple proxy, with this token instead; third, Advanced: Maple Harness without a proxy of its own; then Claude Code and OpenCode.How they connect, with single sign-on on: first, Their own Maple proxy: sign in with their company account, with maple-proxy chain connect --sso and the hub's sign-in address, or maple-harness proxy connect --sso, and the note that Maple Harness keeps using that local proxy; second, Their own Maple proxy, with this token instead; third, Advanced: Maple Harness without a proxy of its own; then Claude Code and OpenCode.
The same lines with single sign-on on: signing in comes first. A demo setup.

The token line for Maple Harness alone is the advanced way, for places where no proxy of their own can run. On their own proxy, Test the connection recognises the token as theirs ("Connected as <person> at <hub>: your requests count as you"), leaves Use the hub's people and teams here, and send usage up unticked and greyed out (that needs a chain token from the hub's admin), and Save keeps it: see Join with a personal token and Which setup do I need?.

The same works from a terminal on the proxy's machine: maple-proxy token add <label> --person <id>. Through single sign-on, an admin can make tokens too (the proxy scope only, and they always expire: 90 days unless the admin chooses).

Signing in with your company account #

When your admin turns on developer sign-in (Single sign-on, Developer sign-in), open the single sign-on address and sign in. Depending on how it is set up:

  • Automatic: you are added as a person at your first sign-in (your team comes from your groups), and land on My access.
  • Ask an admin: your first sign-in says Request sent. Once an admin accepts it on People & teams, sign in again.

My access is a page of its own: you never see the admin pages, and nothing there can change anyone else's access.

My access for ben@acme.example, person ben on team backend: Connect your tools, its first lines Your own Maple proxy (signs in through this page) with maple-proxy chain connect --sso and the Maple Harness shortcut maple-harness proxy connect --sso, then Maple Harness with a token, Claude Code and any OpenAI-compatible tool; Connect your proxy with a code field; Your tokens with your proxy (renews itself) and ben laptop expiring 2026-11-11; Make a token; and Your usage for the last 30 days.My access for ben@acme.example, person ben on team backend: Connect your tools, its first lines Your own Maple proxy (signs in through this page) with maple-proxy chain connect --sso and the Maple Harness shortcut maple-harness proxy connect --sso, then Maple Harness with a token, Claude Code and any OpenAI-compatible tool; Connect your proxy with a code field; Your tokens with your proxy (renews itself) and ben laptop expiring 2026-11-11; Make a token; and Your usage for the last 30 days.
My access, a developer's own page.
  • Connect your tools: the lines to copy. The first, Your own Maple proxy (signs in through this page), are the commands that sign your proxy in (below); then a token for Maple Harness the advanced way, for Claude Code, and for any OpenAI-compatible tool.
  • Connect your proxy: where you type the code your proxy shows when it signs in (below).
  • Make a token: name it (your laptop, CI). It expires after the number of days your admin set (30 by default), has the proxy scope only, and is shown once.
  • Rotate: a new secret for the same token and a fresh expiry; the old secret stops at once.
  • Revoke: it stops at once.
  • Your usage: your own requests, tokens and AI units for the last 30 days.

Your account is matched by your identity at your company's provider, recorded at your first sign-in, never by your email address alone: an address that belongs to someone who signs in with another account does not take over their access.

Sign your own proxy in #

On your own machine, Maple Harness talks to its own proxy, and your other tools can too. To use the team hub, that proxy signs in to the hub with your company account, and the hub gives it a token for you. There are three ways to start it, and they are the same sign-in: one started in one place shows in the others, and any of them can end it.

WhereHow
Your proxy's setup pageHubs & chaining, Connect this proxy to a parent hub, Sign in with your company account: type the hub's sign-in address (this single sign-on address) and Sign in with your company account
A terminal on your proxy's machinemaple-proxy chain connect --sso https://maple-admin.example.com
Maple Harnessmaple-harness proxy connect --sso https://maple-admin.example.com: a shortcut that starts your local proxy if needed and has it sign in; the harness itself is not signed in and gets no token

Each shows a link to My access and a short code. Open the link in a browser on any device (a phone works, so does a laptop next to a server you reached over SSH), sign in, and type the code under Connect your proxy, then Check the code. The page says which proxy asked, by its name, from which address and how long ago, and asks Is this your own proxy? Everything it sends here counts as you. Press Yes, connect it only if it is the proxy you just used: whoever started the sign-in gets access as you. No, refuse it tells that proxy no.

Connect your proxy on My access: the code typed in, and the question: A Maple proxy named ben-laptop asked just now from an address, which is the address this browser uses. Is this your own proxy? Everything it sends here counts as you. Buttons Yes, connect it and No, refuse it.Connect your proxy on My access: the code typed in, and the question: A Maple proxy named ben-laptop asked just now from an address, which is the address this browser uses. Is this your own proxy? Everything it sends here counts as you. Buttons Yes, connect it and No, refuse it.
Connect your proxy: which proxy asked, before anything is granted.

From Maple Harness it looks like this (the addresses, code and dates are examples):

$ maple-harness proxy connect --sso https://sso.acme.example:12464
Your local proxy is signing in to sso.acme.example:12464. Open this address in a browser (on any device), sign in with your company account, and enter the code:

    https://sso.acme.example:12464/sso/access

    88HB-6KCR

The hub's page names your proxy, so check the name it shows. The code works until 14:32. Waiting…
Your local proxy is now signed in to sso.acme.example:12464 as ben@acme.example; the harness keeps using your local proxy.
The hub's models are reached as hub/<model> (pick one with /model), counted at the hub as you. The proxy renews the sign-in by itself until Mon 19 Oct 14:22.

What you get:

  • Your proxy holds a token for you, with the proxy scope only, in its secret store. It adds this hub as a provider (named hub unless you choose another name), so its models work as hub/<model> in every tool that uses your proxy.
  • Everything your proxy sends counts as you: your budget, your models and your accounts here.
  • The token lasts 12 hours and your proxy renews it quietly, for up to 7 days after you approved it. Then it asks you to sign in again, on its setup page (Sign in again) or with the same command.
  • On My access the token is listed as your proxy (renews itself); revoke it there to cut that proxy off at once. To end it from the proxy, use Disconnect on its setup page or maple-proxy chain disconnect: the token is revoked at the hub as well.
  • A hub or a proxy before 2.2 cannot do this, and a hub with developer sign-in off refuses it: your proxy says so, and you use a token from your admin instead.
  • No company-provider token is kept anywhere: the hub is what renews your proxy's access, and it stops renewing when an admin revokes your token, forgets your sign-in, removes you, takes you out of the developers' domains or groups, or turns developer sign-in off.

The full steps, with screenshots of your proxy's side, what it shows when the sign-in needs attention, and when to use a chain token instead: Join your laptop to a team hub.

Behind a company HTTP proxy, set HTTPS_PROXY as usual (and NO_PROXY for internal hubs) where your proxy runs: its sign-in and renewals go through it, encrypted end to end with the hub.

Advanced: a token for CI and containers #

Where no proxy of your own can run (a CI job, a container), Maple Harness can use this proxy directly with a token, from an admin or made on My access:

maple-harness proxy connect https://maple.example.com:11535

It asks for the token without showing it (or reads it from standard input), keeps it in the secret store and writes harness.proxy in its config.yaml. maple-harness proxy status says where the proxy is, and maple-harness proxy disconnect goes back to the proxy on that machine. Such a token does not renew itself. See Connect the harness to a proxy.

What admins see #

On People & teams, each person's Access and tokens says how they sign in (tokens from an admin, or single sign-on with their provider and email) and lists their tokens as above, with Forget their sign-in (their next sign-in is matched again; their tokens work until they expire, and their proxies' sign-ins stop renewing).

An id given to someone else. A sign-in belongs to the person it was made for, not just to their id: each person has a sign_in_marker in config.yaml, written by the proxy (leave it as it is). Remove a person and add someone else with the same id, on the setup page, with maple-proxy people, or by editing config.yaml while the proxy is stopped, and the old person's accounts do not sign in as the new one; what was made for the old person is cleared (Recent activity shows sso.prune) and the tokens they made for themselves are revoked. With settings from files (a ConfigMap) the proxy cannot write the marker. There, a person without a sign_in_marker line is told apart by the addresses setup_page.sso.people names them by: an id given to someone with other addresses (or none) is someone new: within seconds of the proxy reading the file, the old account stops signing in, what was made for it is cleared and the tokens it made for itself are revoked (sso.prune, reason=identity_changed). Team, budget, model and account edits never end a sign-in. A marker line, when there is one, wins. When the old and the new person share an address, have none, or keep the same marker, change the marker or use Forget their sign-in (or maple-proxy people forget-signin <id>) (Kubernetes).

Above the people, when something needs a look:

  • Asked to use this proxy: developer sign-ins waiting for you (ask-an-admin mode), with Accept (as a new person, or as someone already there, with a team) and Refuse. A sign-in whose email belongs to someone who signs in with another account is marked email in use: accept it only for the right person.
  • People who cannot connect yet: people with no live token, tokens never used, and tokens that expire within a week.
  • Refused sign-ins of the last seven days, and why.
Asked to use this proxy: cara@acme.example from id.acme.example, her groups giving team design, with As a new person, team design, Accept and Refuse on one line; People who cannot connect yet: ana has no token; and Refused sign-ins, last 7 days (1), folded.Asked to use this proxy: cara@acme.example from id.acme.example, her groups giving team design, with As a new person, team design, Accept and Refuse on one line; People who cannot connect yet: ana has no token; and Refused sign-ins, last 7 days (1), folded.
A developer waiting for an admin.

Expiry, renewal and revoking #

TokenExpiresRenewed
Made by an adminNever, unless they chose a date (through single sign-on: 90 days unless chosen)No
Made on My accessAfter developers.token_days (30 by default, at most 90)Rotate gives a fresh one
Your proxy's, signed in with your company account12 hoursQuietly, for up to 7 days after the approval

A revoked or expired token stops at once on every replica of a shared proxy. Proxies chained below a hub stop accepting it when they next fetch the hub's list: within seconds while the hub can be reached (they wait on the hub for news), about a minute (chain.directory_interval) after a failed fetch, and while the hub cannot be reached at all, up to chain.directory_grace (15 minutes by default), after which they refuse every token from the hub until it answers again. The same goes for the old secret of a renewed proxy token. Revoking never comes undone by a renewal.

Removing a person revokes the tokens they made for themselves (on My access, and their proxies'); the tokens an admin made for them keep working, unattributed, unless you revoke them too (the remove confirm offers it).

Limits #

  • A developer may hold 5 live tokens (developers.max_tokens) and make 10 an hour.
  • Automatic onboarding adds at most 50 people a day; more sign-ins wait for an admin.
  • With settings from a ConfigMap, developers cannot be added or make tokens themselves (My access says so): an admin gives them one.
  • A proxy with replicas, with settings from a ConfigMap, or with read-only mounted secrets cannot keep a sign-in: connect it with a chain token from the hub's admin (Chain proxies into hubs).
  • Tested against a stand-in identity provider, in Chromium through a TLS front, with a real local proxy signing in from its page and from the terminal. Not yet run against real Google, Microsoft Entra ID, Okta or GitHub accounts.

Made with ❤️ by Kinn Coelho Juliao in Ottawa, eh — fuelled by double-doubles, bud. 🍁