Repository navigation
v0.13.1
Exeris Kernel v0.13.1 — Release Notes
| Artifacts | eu.exeris:*:0.13.1 |
| Date | 2026-10-30 |
| Predecessor | 0.13.0 |
| Framing | Pre-1.0 / TRL-3. A patch release on the 0.13 line. Per-surface semver policy: docs/stability-matrix.md. |
Scope of these notes. They describe behaviour published in this repository, taken from the
[0.13.1]section ofCHANGELOG.md. 0.13.1 changes no SPI type and adds no
MIGRATION.mdsection.
Summary
0.13.1 makes the Community SecurityProvider usable without code. In 0.13.0 the provider that
ServiceLoader discovers holds no verification key and no configuration key supplies one, so a
Community kernel denies every bearer token and every route that requires one answers 401. In 0.13.1
three configuration keys give it a JWKS endpoint, an issuer and an audience.
Nothing else changes. An application that sets none of the three keys behaves exactly as on 0.13.0.
Security: token verification keys from configuration (ADR-040)
| Key | Meaning |
|---|---|
security.jwks.uri |
The JWKS document tokens are verified against: an absolute http or https URI with a host. |
security.jwt.issuer |
The iss claim a token must present. |
security.jwt.audience |
The aud claim a token must present. |
- All three or none. With none set, the Community provider holds no key and denies every token, as
in 0.13.0. With all three set, it verifies tokens against a key set fetched from the endpoint on the
first token and rotated underKeyRotationPolicy.defaults(). Any other combination fails the boot
withEX-BOOT-0002, naming the first missing key. So does asecurity.jwks.urithat is not an
absolutehttporhttpsURI with a host. - The key set is built when the security subsystem starts. An
httpsendpoint is fetched only
over TLS that verifies the server. It needs a crypto provider bound andexeris.transport.tlsnot
false. Otherwise the boot fails withEX-BOOT-0002, withEX-NET-4004as its cause. Anhttp
endpoint is plaintext by the operator's request. - Shutdown releases the client engine. The provider denies every token after the security
subsystem stops. - Only the Community provider reads the keys. A
SecurityProviderthat outranks it, such as an
Enterprise overlay or one an application registers with a higher priority, is bound unchanged, and the
keys are not read.
An embedding host that builds the provider itself can call
CommunitySecurityProvider.overJwksEndpoint(URI, KeyRotationPolicy, Clock, String, String). It returns
an AutoCloseable provider over the same rotating key set. It builds the client engine when called,
so it needs the memory allocator and, for https, a crypto provider bound at that point.
Reference: docs/subsystems/security.md,
docs/subsystems/config.md.
Compatibility and upgrade
- Compatibility impact: additive. No SPI type changes. The SPI compatibility gate has nothing to
report. - Community API additions:
CommunitySecurityProvider.overJwksEndpoint(URI, KeyRotationPolicy, Clock, String, String), andCommunitySecurityProviderimplementsAutoCloseable. - Upgrading from 0.13.0 is a version change. A deployment that already sets any of the three keys
for another purpose now has them read by the Community security subsystem. If not all three are set,
the boot stops and names the missing key. - A host that registered its own
SecurityProvideronly to supply keys can drop it and set the
three keys instead. While its provider outranks the Community one, nothing changes for it.
Known limitations and not covered
- The rotation tunables of
KeyRotationPolicy(overlap window, stale-fetch budget) have no
configuration key. The defaults apply. - One JWKS endpoint, one issuer and one audience. Several identity providers behind one Community
SecurityProviderare not configurable through these keys. docs/subsystems/security.mdanddocs/subsystems/config.mdgained the new keys and behaviour. A
whole-page re-verification of either page against the code is not part of this release, and their
last-verifieddates are unchanged.
Verification
Measured at the cut, 2026-10-30:
- Full reactor at
0.13.1on the sources ofbb5fd7c8,mvn clean installon Temurin 25, with a
local repository holding noeu.exerisartifact, so every module resolved from the reactor: BUILD
SUCCESS, and the installed jars carry0.13.1. Its test reports were not archived; the CI runs below
are the record. - The release branch's CI on its final commit before the cut,
e6f4f07e, run
41025009935: every job
green — Build & TCK Verification, SPI Compatibility Gate, JFR Reporter build & tests, Persistence
RLS/Interceptor Gate, Kafka Integration Gate, Recovery Continuity Gate, Transport Stress Gate, TLS
OpenSSL 3.5.6 and TLS OpenSSL 4.0.0. The per-job test reports are that run's artifacts. - After
e6f4f07ethe line changes the 13<version>elements, documents, and the order of
CommunitySecuritySubsystem.start(), which builds the key set last. The CI of the
release(0.13.1)pull request intomain(#816) runs on the line's final commit.