Releases¶
JANUS documentation is versioned alongside the JANUS product. Each release of the product maps to an immutable documentation version, and the default site always shows the current stable release.
Current release¶
| JANUS release | 1.1.0 |
| Documentation version | 1.1.0 |
| This site | current stable |
The documentation version tracks the JANUS release version: the page you are reading describes the behaviour of JANUS 1.1.0. Package names, paths, unit names, ports and commands in this documentation are those shipped with that release.
Release 1.1.0 is a minor release on the 1.0 line. It ships the
device-authentication, enrollment, revocation-ordering and resilience work of the
NC-P0 R5B.12 campaign as versioned platform packages, and it fixes three defects
found while certifying it: /readyz no longer panics on a gateway domain that has
no safety record, a lost apply acknowledgement can no longer wedge a domain so
that it stops receiving later revocations, and the desired-state ordering record
is fsynced like its sibling record. It ships no new default: device
authentication stays opt-in, the safety gates that were off in 1.0.4 remain off,
the client's compiled -apply-mode=legacy default is unchanged, and migration
000047 is not included. Ten additive migrations (000037–000046) are applied
by the Controller at start-up; none drops, renames or backfills. Two limitations
are unchanged and stated deliberately: revocation is enforced by the Gateway on
its next successful contact and has no published SLA, and a Gateway that cannot
reach its Controller continues to enforce the last authority it received —
indefinitely, with no lease.
Release 1.0.4 is a patch release on the 1.0 line. It corrects the host-local break-glass administrative recovery lifecycle so that recovery works repeatedly for the life of an installation instead of only once on a fresh database. Break-glass now uses a single, stable recovery principal — enable and disable toggle its state and time window, and rotate replaces its credential in place — so a second enable after a disable no longer collides on the recovery login locator, rotation invalidates any live recovery session, and any malformed historical recovery state is converged without deleting security history. Identity and recovery semantics only: no desired state, authorization, reconciliation or data-plane behaviour change.
Release 1.0.3 is a patch release on the 1.0 line. It corrects the Site
Connection health classifier so a healthy, fully-converged Site Connection is no
longer reported as Degraded. Applied-ness is judged on the compiled-state
identity rather than the provenance Git revision (a desired-state revision
that does not change a gateway's effective state legitimately leaves the applied
Git revision behind without requiring a re-apply), the delivery success state
validated is recognised, and a merely old WireGuard handshake no longer
degrades a healthy tunnel. Observation and classification only: no desired state,
authorization, reconciliation or data-plane behaviour change.
Release 1.0.2 is a patch release on the 1.0 line. It repairs New-UI operational parity and scope integrity: an Intent link from a Tenant-scoped list no longer falls back to Platform scope, and the Tenant desired-state objects (Sites, Resources, IP Networks, FQDNs, Groups, Services and Service Groups) now expose their supported create / review / submit / detail / edit / delete paths in the New UI, reusing the same authoring, validation and audit pipeline as the Classic UI. No feature or behaviour change beyond restoring existing capability.
Release 1.0.1 is a patch release on the 1.0 line. It fixes a
browser-visible regression in the presentation-layer (Interface) switcher: the
switcher link was rendered as a scheme-relative reference (//interface?…), which
a browser resolved with interface as the hostname, so selecting the other UI
layer navigated away from the JANUS origin ("Safari Can't Find the Server"). The
switch target is now an origin-relative path, and both directions (Classic → New
and New → Classic) are covered by regression tests. No feature or behaviour change
is included.
Release 1.0.0 is General Availability. It is a closure release: it
promotes the v0.23.0-certified product to stable with no new milestone or
feature cycle. The official release packages pin the Korves.Net Entitlement
Manager authority endpoint and the Vendor Root trust anchor at build time, so
commercial-admission enforcement is effective in the released Controller (the
authority endpoint and root are never customer-configurable).
Release 0.23.0 is the entitlements & licensing milestone. JANUS is now a licensed product: the managed control plane admits connectivity only while a current licence — a vendor-issued entitlement — is in effect, and that enforcement is a property of the released packages rather than a runtime switch you can disable. The commercial authority is the separate JANUS Entitlement Manager, which owns the vendor-side commercial record (customer organisations, seller entities, contracts, products, prices, subscriptions, invoices and EN16931 Factur-X documents) and issues and renews the signed entitlements a Controller consumes; a third-party payment provider is integrated only as a payment adapter and is never commercial or entitlement authority. Licensing never changes what the product may disclose or how authorization works for a licensed deployment, and there is no throughput throttling by licence tier.
Release 0.22.0 is the localization milestone: JANUS gains a first-class interface-language framework with English and German, a per-principal language preference and a platform-level default, a compact language switcher on the sign-in page and the application shell, complete localization of the production scope (the primary WebUI, the self-service Portal, the Site Edge local setup UI and the client-side JavaScript), locale-aware presentation and formatting, and localized labels and help for the desired-state object editor. Interface language is presentation only: it never changes authorization, authentication assurance or what the product discloses, and English remains the canonical fallback. See Interface language.
Release 0.21.0 adds LDAP and Microsoft Active Directory (AD-semantics) identity integration: external identity-provider administration scoped to the platform or to a single deployment, a stable external identity that is not email matching, identifier-first sign-in with safe provider routing, external-group to explicit Role × Scope mapping, the mandatory administrative multi-factor requirement and step-up, and local administrative recovery. Real Microsoft AD DS interoperability is validated against the available LDAP/OpenLDAP and Samba AD compatibility environments; validation against a Microsoft Windows Server AD DS environment is deferred to a later campaign.
Release 0.20.0 is the enterprise identity-federation and OIDC productisation
milestone: managed OpenID Connect providers in management state, platform and
deployment provider scopes with cross-deployment isolation, a dedicated
scope-aware provider:admin permission so a deployment administrator can
administer their own deployment's providers without platform-wide authority,
secret-safe provider diagnostics, external group mappings to explicit Role × Scope
authority, explicit identity link/unlink, a JIT policy, fail-closed IdP-outage
semantics, a mandatory administrative MFA floor with no configuration bypass, and
a local administrative recovery authority independent of external IdPs.
Authentication is never authorization, and the OIDC authorization transaction
remains browser-bound. LDAP/Active Directory, SCIM and SAML are not part of
this release. See External identity federation.
Release 0.19.0 is the identity, authentication-security and RBAC milestone: multi-factor authentication (authenticator app and passkey), recovery codes, authentication assurance and step-up, human-operable administration of administrative identities, roles, bindings, service principals and API credentials, a per-scope MFA policy, and the invitation-to-configuration end-user journey. See Identity and access.
Release 0.19.1 is a security-correctness patch on the 0.19 line. It binds an OIDC authorization transaction to the browser that started it, so a callback captured and presented from a different browser is refused instead of logging that browser in (login CSRF / session fixation). It ships no new feature.
Post-release maintenance tags on the 0.18 line (v0.18.1, v0.18.2) shipped
no product change — only release-pipeline and documentation-publishing
corrections — so the behaviour of the 0.18 documentation is unchanged.
How versioned documentation works¶
https://docs.janusaccess.net/ -> current stable documentation
https://docs.janusaccess.net/<major>.<minor>/ -> immutable, per release
- The bare site always serves the current stable documentation.
- Every release is also published under an immutable
<major>.<minor>path (https://docs.janusaccess.net/0.18/), which keeps describing that release unchanged as later releases ship. - A released documentation version is immutable: correcting documentation does not move an existing release version. A documentation-only correction is published as its own revision against the same product version, so the release page never silently changes under a reader.
- Release notes are published with the JANUS product itself.
Supported platforms¶
| Component | Package | Supported platform |
|---|---|---|
| Controller | janus-controller |
Debian 13 (trixie), amd64 |
| Gateway | janus-gateway |
Debian 13 (trixie), amd64 |
| Site Edge | janus-site-edge |
Debian 13 (trixie), amd64 |
| Client (Linux) | janus-client |
Linux; released from the janus-client repository |
| Operator CLI | janus-cli |
any host with ca-certificates |
The JANUS Native Client is built and released from its own repository
(janus-client), on its own version line; it is not built or published from
access-concentrator. The row above is listed for reference only. The public,
versioned Client Contract (clientcontract) and the server-side manifest
assembly remain in access-concentrator.
The Gateway and the Site Edge rely on in-kernel WireGuard support and on
nftables; no out-of-tree module or DKMS build is required. The Controller
supports a local or external PostgreSQL identically, and any compatible
reverse proxy or ingress (Caddy in the reference deployment, or nginx, HAProxy,
an F5, a Traefik, an ALB, …) may front its listeners.
Supported / unsupported boundary¶
Documented deliberately, so a boundary is not mistaken for a feature.
Supported
- Declarative, Git-backed configuration reconciled into a per-Gateway desired state and applied by the Gateway.
- Multi-tenant control plane: Tenants, Deployments and Gateway nodes are separate concepts, and a Gateway node may serve several Deployments in isolated runtime domains.
- WireGuard-based remote access with fail-closed forwarding.
- Site Edge participation: a JANUS participant representing a customer site whose existing firewall or router is not reconfigured.
Not supported in this release
- No NAT66 anywhere in JANUS. Internet egress over IPv6 is routed and filtered/authorized normally; no NAT66 is synthesized as a fallback.
- One provider attachment per Site Edge, and no automatic Site Edge HA. Several edges may exist for redundancy, ordered declaratively, but failover is not automatic.
- No local breakout on a Site Edge: customer traffic is never sent directly to the Internet from the edge host; all egress is carried to the provider Gateway.
- No local management UI on a Site Edge. The central WebUI and API are the management surfaces.
- No dynamic routing protocols (for example BGP/FRR). Routing is declarative and static.
- No automatic MTU/PMTU derivation. An MTU may be supplied in a plan and is applied, but JANUS does not measure or derive a path MTU.
- No throughput throttling by licence tier. A licensed deployment uses the throughput its hardware, network, data plane and policies can deliver.
- No LDAP / Active Directory, SCIM or SAML. External identity federation in this release is OpenID Connect only; LDAP/AD is the next milestone and is not shipped here.
- The Client is a Linux daemon; it reports
UNPROVISIONEDuntil its manifest and private key are provisioned, and the package ships neither by default. It is built and released from thejanus-clientrepository, not from here.
Distinctions that hold across releases¶
Three distinctions are load-bearing and are never relaxed:
- Capability ≠ Entitlement ≠ Placement. What a Gateway can do, what a Tenant is entitled to, and where a workload is placed are three separate decisions. A capable node alone grants a tenant nothing.
- Desired state ≠ applied state. The Controller records intent; the Gateway records what it actually applied. They are reconciled, and the difference is observable.
- Enabled is an access state, not an activity state. Whether an object is configured to permit access says nothing about whether anything is currently connected.