* feat: add domain virtual responses with a compact editor and bounded edge matching
* fix: keep traffic working during rolling edge script updates
* refactor: centralize edge management transport
* fix(mail): persist mail logs, fail2ban database and ignoreip across engine updates
Mail engine updates recreate the container (docker rm -f + docker run),
so anything not on a bind mount is lost: /var/log (mail.log, dovecot and
fail2ban logs), fail2ban's SQLite database, and operator ignoreip
customisations in /etc/fail2ban.
- Bind-mount /var/log and /var/lib/fail2ban from the host mail state dir.
Deliberately not /etc/fail2ban: a seed-once mount would hide later image
changes (same trap as #392's master.cf).
- Render operator ignoreip additions (OPENSHIP_MAIL_F2B_IGNOREIP, passed
through engine.env) into a jail.d override on every boot, as baked
jail.local value + operator value, so image defaults are never dropped.
- Run cron under supervisord so logrotate's daily job actually fires for
the now-persisted logs; logrotate is installed explicitly (only a
Recommends of rsyslog) and build-gated.
Fixes#1701
* Preserve existing mail state before replacement and repair supervised log rotation
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* feat(dns): add DigitalOcean DNS provider support
- Add DigitalOcean DNS management for custom domains and DNS-verified HTTPS
- Preserve record ownership with paired TXT markers and update provider setup guidance
* fix(dns): parse DigitalOcean record IDs from formatted JSON
- Handle compact and pretty-printed API responses, with a fallback when Python is unavailable
- Cover record cleanup and API error responses in DNS hook tests
* fix(dns): harden DigitalOcean DNS provider after review
- Decode TXT input before writing so quoted values compare in-sync
- Treat zones not delegated to DigitalOcean nameservers as pending
- Resolve zones with one paginated domain list and strip wildcard labels
- Carry credential id and provider on unauthorized lookups so the
reconnect modal targets the rejected credential
- Clean up ownership markers when the marked record is already gone
- Report read-only token verification accurately and surface missing
write scope on 403
- Guard token redaction and requests against an empty token
- Share DNS name helpers and the DNS-01 cleanup hook template
* fix(dns): release owned records from inactive DigitalOcean zones
- Allow DNS cleanup to resolve inactive zones while keeping writes restricted to active zones
- Fetch DigitalOcean records and ownership markers concurrently
* fix(dns): resolve provider credentials oldest first
* Require strict JSON record IDs before DNS challenge cleanup
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* fix(api): stamp PAT token id on REST audit rows and audit token reads
Two gaps in the audit log, both from the same root: a REST call made
with a personal access token left no trace of WHICH token made it, and
a successful read made with a token left no row at all — while the
same read through MCP was audited with the token id attached.
- resolveCallClientId now falls back to the credential the auth layer
already resolved: a token principal's session id IS its canonical
principal id (pat:<id> / oauth:<clientId>), minted from the
hashed-token lookup, not from anything the caller supplies. The
nonce-signed MCP claim still wins. Browser sessions never reach the
fallback (no principalKind), so a cookie session id can never land
in the column. Shared operations and the deployment create path use
the same resolver, so their rows gain the token id too. No schema
change: the column was documented for exactly this value.
- The route emitter now audits successful reads/lists by token
principals (PAT / OAuth) — a script holding a token gets the same
"what did it look at" treatment MCP already gives its reads.
Browser reads stay unaudited (too noisy), failed reads are still
not logged, and operations that already recorded the call still
skip the emitter. One exception: reads of the audit log itself are
not audited — every such read would append a row to the log, so its
total could never be stable and its facets would be dominated by
whoever reads it most.
Fixes#1703
* fix(api): clear the error-boundary gate and the tokens parity expectation
The error-boundary gate flagged the pre-auth catch in
resolveCallClientId as unobserved. It only runs when no
RequestContext exists yet, so there is no credential to derive
from: mark it with the repo's diagnostics-ignore marker.
The tokens SDK-parity audit test listed only the three MCP rows,
but token reads are now audited by design, so the two remote
token-client reads in that test add two settings:read rows.
Expect them, matching the settings/webhooks parity updates.
Fixes#1703
* fix(api): avoid duplicate MCP read audit events
* fix(api): simplify audit coverage and reject malformed nonce bytes
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* perf: reuse Docker builders and parallelize independent Compose work
* test: exercise declared dependency gates on the isolated Docker host
* fix: preserve dependency ownership and native cache maintenance
* fix: drain dependency readiness failures through the shared task barrier
* test: align server recovery expectations with source scan recovery
* fix: retain released dependency providers during publication recovery
* Keep route verification and bound parallel deployment work safely
* Send scoped cancellation confirmations through the customer email queue
* Offer help without treating one canceled subscription as account churn
* Invite cancellation feedback and offer direct support
* Preserve native Docker dependency cache across source changes
* Keep runtime dependencies ahead of changing API source
* Split independent Docker regression suites across CI jobs
* Use fresh connections for routing configuration probes
* Show published deployments while final startup verification runs
* Complete verification translations and align test types
* feat(billing): unify plan management and referral navigation
* docs(billing): describe plan management and align summary assertions
* test(billing): align named plan and accessible summary assertions
* fix(services): say why an environment apply did not start
A failed environment apply only said the service did not start. Name the
cause from the replacement container's state: its exit code, restart
count, out-of-memory kill, Docker error or failed health check.
Refs #1613
* fix(runtime): redact environment values from apply failure diagnostics
* test(runtime): keep diagnostics regressions separate from command apply tests
* fix(runtime): redact command-only and escaped credentials during env apply
* fix(diagnostics): bound literal redaction and preserve structured startup reasons
* refactor(runtime): share deployment stability checks with environment apply
* fix(diagnostics): share redaction without hiding credential syntax
* fix(diagnostics): keep raw task and notification errors out of reports
* refactor(diagnostics): prefer structured provider failure summaries
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* fix(edge): serve a static site's 404.html for missing paths
* fix(routing): make static SPA fallback explicit and preserve defaults
* test(routing): update static fallback checks and run HTTP coverage
* fix(i18n): complete inbound alias guidance across locales
* test(monitoring): isolate the session in stream fixtures
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* fix(deploy): keep loopback-port deploys working without a host channel
On a raw compose install with no host channel, every deploy failed after
the image build with "Cannot read Openship edge routes: neither Docker nor
bare OpenResty inventory is available", even though the deploy log says
host-side edge/routing steps are skipped. The loopback-port preflights read
the strict edge inventory through the demoted host executor, which refuses
every call.
Fixes#1625
When the host executor is one we demoted for having no usable channel, the
preflights now get an inventory they can read — an empty one — so
allocation rests on durable claims alone, exactly like the unscanned
live-port pick. A real conflict still fails loudly at the Docker bind.
Covers both the compose deploy preflight and the single-container
preflight (plus its port-conflict alternative path). The route-apply
safety gate is untouched: refusing a loopback route on an unreadable edge
stays deliberate there.
Test: new case in compose-host-channel-notice drives a loopback-port
compose deploy with the real demoted executor and asserts the edge proxy
handed to the preflight resolves to an empty inventory; it failed with
the reported error before this change and passes after.
* fix(deploy): inventory socket edge routes before allocating ports
* test(deploy): share edge inventory fixtures across allocation paths
* test(routing): resolve inventory from the simulated edge config
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* test: match SMTP fixtures to required TLS
The mail transport now requires TLS, so the plaintext fake server in the cloud support test failed every send. The STARTTLS check also raced the fixture's stdout.
* test: wait for SMTP deliveries before asserting
The fixture reports deliveries over stdout, so a resolved send can arrive before the line does.
* fix(api): reject permission tags pointing at nonexistent resources
parsePermissionTag validated the action and root segments but never the
leaf, so a typo like project:servcie:write passed the boot scanner that
claims to catch tags pointing at nonexistent resources. Validate the leaf
against the known resource set with a clear error naming the bad value.
* fix(permissions): derive tag validation from shared resource definitions
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
* feat(auth): add generic oidc login for self-hosted dashboards
Register a Better Auth generic-oauth provider (id oidc) when OIDC_ISSUER, OIDC_CLIENT_ID and OIDC_CLIENT_SECRET are all set, advertise it with its OIDC_DISPLAY_NAME label, and render it on login and registration. Existing users link only when the IdP sends email_verified true, the invite-only gate still applies, and zero-auth instances reject the OAuth2 routes. Refs #1469.
* fix(auth): verify oidc id tokens against the issuer jwks
Verify the ID token signature against the discovered JWKS with the configured issuer, client audience, time claims and authorized party, and fail closed instead of falling back to userinfo. Require discovery issuer equality, require https for production endpoints except loopback, and route the code exchange through the validated token endpoint. Addresses review on #1489.
* fix(auth): validate the oidc authorize endpoint and expire discovery
Refuse OIDC sign-in unless discovery validates, require and pin the authorization endpoint the redirect uses, expire cached discovery after one hour and fail closed on a failed refresh, and cover the production issuer boot check. Addresses review on #1489.
* refactor(auth): inject the oidc discovery loader into account security
Pass loadOidcDiscovery through the plugin options like getAuthMode instead of a lazy import, so the module keeps no runtime dependency on the env-loading provider code.
* fix: verify OIDC identities and bind tokens to sign-in state
* fix(auth): isolate OIDC identities and enforce self-hosted login boundaries
* test(auth): align SDK parity config mock with OIDC policy
---------
Co-authored-by: Hydra <abdelhamedmo59@gmail.com>
resolveServerIdForProject returned null for a project with no active
deployment, and resolveSslProvider fell back to the local host-server.
A never-deployed project bound to a remote server therefore had its
domains verified and its certificates requested on the Openship host.
PR previews verify their domains before the first deploy, so on a
remote server every preview stuck at "Preview domain is not ready".
Both resolvers now use project.serverId when there is no active
deployment. The organization ownership check is unchanged, and a
deployed project still resolves from its deployment snapshot.
Closes#1497
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add runtime security advisories and annual Cloud billing
* fix(updates): show runtime advisories in the global update center
* fix(updates): synchronize advisory consent across global views
* refactor(updates): reuse normal refresh and environment flow
* fix(security): pin patched Node and Bun runtimes across releases
* fix(build): pass bootstrap selection independently of eval arguments
* test(build): expect the patched default Bun image in detection
* docs: prepare 0.9.4 changelog since 0.9.3