Users were asked to sign in again every ~30 minutes, even while active.
Session lifetime
- Browser: UDS_SESSION kept its login-time Max-Age and was never re-issued,
so the cookie vanished 30 min after login. Re-issue it on use (throttled
by slidingInterval).
- Desktop: remote.mux WS traffic never passed the HTTP auth middleware, so
the idle TTL never slid. assertPrincipalLive now reports activity and
slides the session and the account's bridges (throttled).
- New setting sessionIdleTimeoutHours (Settings page + config). Default 0 =
no automatic sign-out; only a manual sign-out ends a session, so
conversations and night-time cron are never cut off. 0.5-168 enables an
idle timeout with the 7-day cap. The TTL is read live.
- Stores support long TTLs: the absolute cap follows the TTL, older 7-day
sessions are lifted on activity, and expiry timers re-arm instead of
overflowing setTimeout (~24.8 days).
UAC token check
- Every 2 hours (and 1 min after start) each QR session's token is checked
against icenterapi. A rejected token is only flagged, never a sign-out.
Network errors, 5xx and bad JSON keep the previous verdict (the old 6h
check revoked all of an account's sessions on any failure, including
outages).
- GET /uds-auth/session-status (non-sliding) returns alive + tokenValid.
The client probes it every minute and on focus: a gone session signs the
UI out with a notice; a rejected token opens a refresh QR once.
- Scanning in refresh mode writes the new token into every live session of
the account and the skill credential cache in place: no new session, no
reload. Other accounts are rejected (token_refresh_emp_mismatch).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
RolesStore.init() now seeds the default emergency password, so a fresh
store starts at generation 1. Two remediation-0310 tests hard-coded the
old absolute versions (3 and 1/2). Compare against the post-init
baseline instead; the queueing and failed-write behavior under test is
unchanged.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Skill credentials follow the DSH session owner, so a chat created under
the emergency account stays owned by administrator after a QR scan and
skills cannot get a UAC token there. The generic "scan QR first" error
hid this.
- Return session_owner_no_uac when the owner is administrator / a local
account, telling the user to start a new session after QR sign-in.
- Name the owner in no_skill_credentials for UAC owners.
- Audit denied outbound calls with session id and owner.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
0.3.16 mapped every post-scan failure to login_finalize_failed, hiding
codes with their own message (bootstrap_required, account_disabled,
registration_closed). Pass those through again and only fall back for
unknown errors.
The bootstrap_required message now includes the scanned employee number
and how to proceed (UDS_AUTH_INITIAL_ADMIN or emergency account login).
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
The QR poll showed a generic "network error" for any failure, and the
server collapsed every upstream failure into an opaque 502 with no log.
- Classify upstream failures (DNS, timeout, unreachable, TLS cert, HTTP
status, bad response) and return host-specific localized messages.
- Report why the post-scan user lookup failed instead of a generic
invalid-credentials error.
- Log the real errno/message server-side for every qr-proxy failure.
- Show the server message in the QR poll UI; keep "network error" only
for failed local fetches.
Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Emergency (fallback / sealed-box) admins lost the workspace sidebar and saw
"sign-in failed / add API key" on DSH Desktop because the remote.mux opens
anonymously at boot and every early call was rejected terminally.
- gateway: anonymous workspace/follow reaches dsh-acl's empty baseline;
anonymous streams are parked until the carrier aborts instead of failing;
anonymous workspace/initializeDefault answers "nothing created"
- request-auth: a dead UDS_SESSION cookie no longer shadows a valid WS ticket
or bridge (sync + async variants used by all callers)
- dsh-acl: /api/* waits (bounded 15s) for the gateway ACL during Host startup
instead of 403, so the Desktop welcome read no longer fails
- desktop-bootstrap: key/account projection is best-effort per reference
- client: emit connection/reset after login so boot-time caches (settings
describe mirror -> Settings > Models) re-read under the real principal
- sessions: absolute lifetime fixed at 7 days (was min(ttl, 7d) = 30 min);
bridge expiry slides with its session; MemoryStore persisted to
sessions.json (bearer hash only, userData AES-256-GCM sealed)
- README: session lifetime/persistence and DSH compatibility notes
Also includes previously uncommitted uds-auth 0.3.x work in this tree.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Shared project and channel sessions were still visible via canViewSystemSessions when the toggle was off; tighten ACL and copy so off means own only.
Co-authored-by: Cursor <cursoragent@cursor.com>
Give admin the same permissions as super/fallback, occupy directoryFlow at priority 1 so the button renders without colliding with the native picker, and inject uiWorkspace for pickDirectory.
Co-authored-by: Cursor <cursoragent@cursor.com>
super_admin/fallback_admin already could; admin now has canCreateWorkspace, and Host-side creates without browser ALS (IM) are no longer blocked as forbidden.
Co-authored-by: Cursor <cursoragent@cursor.com>
Super/fallback can toggle view-all (default on); admin/user stay own-only while still seeing unowned system sessions. Add restore/prune helpers so empty-shell cleanup is explicit and recoverable.
Wire client locale to the DSH host, return stable API error codes with localized messages, and replace bottom refresh with an in-frame retry for expired or offline QR.
Co-authored-by: Cursor <cursoragent@cursor.com>
