Repository navigation
v0.6.0
Upgrade: hub stacks (DataStack CredsStack WebStack), then NetworkStack if you run the private network (the device list and delete routes are answered by the device minter). If an admin had set the dashboard layout from the admin Accounts page, put that value in the config (dashboard: { layout: "sections" | "plain" }) before deploying: the stored value is no longer read and the deployment runs in auto until the block is set.
- Personal access tokens (#52), opt-in with
personalAccessTokens: { enabled: true, maxLifetimeDays? }: every user creates tokens for scripts, CI jobs, command-line tools and remote development machines on a new Access tokens page (user menu) — a name, an optional description, scopes (api,aws,network,shares), an expiry up tomaxLifetimeDays(default 90) and, foraws/api, an optional subset of their roles. The secret (icpat_<tokenId>_<secret>) is shown once; only its SHA-256 is stored, in a newTokensTableinDataStack. A token acts as its owner with the owner's current access narrowed to its scopes and role subset (decided inaccess.ts);apireaches every route the owner could, admin routes only while the owner is an admin; a route outside the scopes answers403withcode: "TOKEN_SCOPE". Tokens cannot create, list or revoke tokens, and plugin routes refuse them. A disabled or deleted owner's tokens stop working; deleting a user deletes their tokens; revoking takes effect on the next request. New routesGET /tokens/current,GET/POST /tokens,DELETE /tokens/{id},GET /tokens/expiry,POST /tokens/expiry/seen,GET /admin/tokens,DELETE /admin/tokens/{id}; the admin Users page gains an Access tokens tab; the bell warns before a token expires and once after. Activity rows written through a token carryactor.token({ id, name }). Discovery gainspersonalAccessTokens.enabled. - Service users carry scopes (#48): an admin picks
aws,network,shares,admin.read.alloradmin.write.allwhen creating one (required onPOST /admin/service-users) and changes them later withPUT /admin/service-users/{clientId}/scopes. The narrow three share the personal-token route table;admin.read.allopens theGETroutes under/adminandadmin.write.allevery/adminroute (it implies the reads). Scopes are read from the registry row on every request, so a change holds from the service user's next call; a route outside them answers403withcode: "TOKEN_SCOPE". Only the admin scopes make a service user an app admin, for the methods they cover; a service user without them vends the roles granted to it and enrolls machines on the private network (POST /network/device-key,ephemeral: true) with nothing else, and anadmin.write.allone manages users and service users like a human admin. Breaking:POST /admin/service-usersrequiresscopes, and every service user is now route-gated. A service user created before this release reads asaws,network,shares,admin.write.all, which reaches the/admin, vending, device-key and share routes; routes outside that table (/requests,/notifications,/preferences,/resources,/plugins) answer403for every service user, so an integration that used them needs a person's session or a personal access token. The Users page's Service users tab gains scope checkboxes on create, scope badges per row, a Change scopes editor and a Network resources section on the panel (service users were already valid resource-grant principals through the API). Activity gainsserviceuser.scopes. The wiki's service-user runbook carries the headless vend-and-join sequence for a VM agent. Personal access tokens are unchanged. - The tenant / project / stage filter popup beside an Account picker (Request a role, the group and role forms) opens leftwards from its button instead of running off the right edge of the panel (#66).
- Dark mode: the Account picker’s dropdown list (Request a role, the admin forms) sits on the solid popover surface like every other floating panel instead of a translucent overlay the page showed through (#57).
- The dashboard layout is deployment config (#56): a new optional
dashboard: { layout: "auto" | "sections" | "plain" }block (defaultauto, validated at synth) reaches the API asDASHBOARD_LAYOUT; the Dashboard select on the admin Accounts page andGET/PUT /admin/dashboard-layoutare gone, and the__dashboard-layout__row in the Resources table is no longer read or written.GET /accounts/homekeepslayoutandsectioned. - Desktop: a saved deployment that nobody could reach at launch (the app reopening after a reboot before Wi-Fi is back, a power-loss restart) is no longer marked unreachable for good: its tab reads · waiting for network and the app re-probes it on its own (every 10 s while offline, then with backoff for about ten minutes once online) before it settles as · unreachable; a host that answers but is not an Infra deployment is unreachable at once. Clicking a waiting or unreachable tab retries it (#58).
- Private network:
POST /network/device-keytakesephemeral: true— the device is removed by the control plane 30 minutes after it goes offline instead of being expired after 7 idle days.GET /network/deviceslists the caller's own devices on every site andDELETE /network/devices/{siteId}/{name}removes one (404 for anyone else's); the Network page lists them under My devices.GET /networkgainsdevShares: { enabled, maxDurationHours }. - Dev shares: a share can be bound to one device (
deviceonPOST /network/shares, the device's name on the site). The port then opens on that device only — resolved by name on every reconciler pass, so a device that re-enrolls under the same name keeps its shares — and always to the owner's own other devices, so a bound share may name no grantees. The one-share-per-port rule applies per device. AdurationHoursabovemaxDurationHoursis now clamped to it instead of refused. In the desktop app the share form gains a Serve from picker when you have other devices on the site, the share card names the device, and a device's relay leaves shares bound to another device alone. - Dev shares:
network.devShares.maxActiveSharesPerOwner(1–200, default 10, checked at synth) sets how many live shares one user may hold — the fixed limit of 10 before; raise it where tools share ports of many machines for one person.GET /networkreports it next tomaxDurationHours. - Threat protection (
loginMethods.threatProtection): a Medium-risk sign-in — in practice a known user on a new network — is now allowed instead of "MFA if configured". Cognito offers only the password on any attempt it applies MFA to, so for a user without TOTP that action removed passkey and email code without adding a second factor. High risk keeps the step-up and, whenemailis configured, emails the user about the attempt. Upgrade:CredsStack. - Sign-in sends Cognito a device fingerprint (
UserContextData, AWS's collector vendored into the web app) on everyInitiateAuthandRespondToAuthChallenge, so threat protection scores a known device on a new network lower than a stranger. When a user's usual passkey or email-code sign-in is missing from the chooser because an MFA action limited the attempt to the password, the page says so in one line. GET /accounts: every role carriessessionDurationSeconds(how long its credentials last).POST /credentialsalways returnsexpiration.apiThrottle: { rateLimit?, burstLimit? }(default 100 rps, burst 200) sets the vending API's stage throttle, which was a fixed 25 rps with a burst of 50 since July. That ceiling applies across every caller — one page load is 10 to 15 calls, so a burst of 50 was three or four people opening the dashboard at once, and the e2e suite tripped it on its own. The per-token WAF rule (waf.perTokenRateLimit) is what bounds one leaked token. Upgrade:CredsStack.- Review fixes before release:
DELETE /network/devices/{siteId}/{name}removes exactly the device listed under that name — a stale duplicate no longer takes the re-enrolled machine (same hostname, suffixed name) with it.GET /network/devicesanswers for the sites that are up when one control plane is down and names the others inunreachable(My devices says so). A device-bound share refuses ahostnamethat is not the bound device's. The per-user token cap holds under parallel creates, andPOST /tokens/expiry/seencounts only the notices it flagged. - Network page: one block per VPC whatever the number of sites — the bar names the VPC, its account and (with several sites) its site as a chip, and carries that site's Connect / Switch & connect; the Shares group and My devices follow. Section chips under the header (one per VPC, Shares, My devices, with counts) scroll to each block. Multi-site deployments no longer nest VPCs under a block per network.
Full changelog: CHANGELOG.md · npm: @fntio/infra-client