
Date: not yet released
*
Date: 2026-11-19
federation.registry.integration.transport: delta loads only changed records from the registry. The registry must support it. Default: legacy.
Requests to hosted entities are answered locally. Disable with federation.resolver.client.local-requests: false.
federation.resolver.lazy builds trust chains at request time: local for hosted subjects, all for all subjects. Default: none.
Resolve accepts explain=true and returns the validation errors as JSON.
Date: 2026-11-12
Connect and read timeouts can now be set for the resolver and registry clients with timeout.connect and timeout.read. Before, a fetch from a host that did not respond could hang for about a minute. See #289.
When the resolver reloads its tree, each part of an entity (Entity Configuration, subordinate listing, Subordinate Statement and trust mark status) that cannot be fetched is taken from the previous load while it is still valid. This also applies to the trust anchor. An intermediate or trust anchor whose Entity Configuration has expired is kept, so its subordinates are still loaded. The export and export-grafana actuator endpoints now show when each entity was last seen, its latest fetch error and the status of its trust marks. In export, uptime.lastSeen is replaced by last_seen. See #285.
A trust mark issuer without a validity duration no longer gives 500. A trust mark without a validity duration is issued without exp and never expires. See #262.
The validity of a trust mark can now be set per trust mark with trust-mark-validity-duration. The value of the trust mark issuer is still used for trust marks without one of their own, and is deprecated.
The resolver now parses, merges and applies metadata policies with the operators from the nimbus-extensions module.
A metadata policy operator with the value null, for example {"value": null}, from the registry is now published as is in Subordinate Statements when Redis storage is used. Before, it was published as {}, so the parameter was not removed. See #276.
Subordinate listings are answered from the records only, without fetching the Entity Configurations of subordinates. Subordinate records must now have entity-types, and is-intermediate for Intermediate Entities, otherwise they are rejected when loaded. See #274.
The resolver and filtered subordinate listings can now fetch an Entity Configuration from an ec_location with a URL-encoded entity identifier, for example <ie>/hosted/https%3A%2F%2Frp.example.se/.well-known/openid-federation. Before, the URL was encoded a second time and the fetch failed. See #281.
The trust_marked and trust_mark_type filters of subordinate listings are only supported by an entity that is also a Trust Mark Issuer, and are answered from its trust mark subjects. Other entities answer 400 unsupported_parameter. See #273.
The service no longer shuts down when the trust anchor cannot be fetched at startup. The first scheduled resolver reload now runs a minute after startup, so a failed initial load is retried without waiting for a full reload rate. See #247.
The resolve and discovery endpoints answer 503 temporarily_unavailable while the resolver has no loaded tree, instead of 400 invalid_trust_chain and 500 server_error.
Releases are published to GitHub Packages instead of Maven Central. Versions up to 1.0.1 stay on Maven Central. Downloading needs a GitHub token, see Using the Artifacts from GitHub Packages. See #275.
Date: 2026-11-02
<ie>/hosted/https%3A%2F%2Frp.example.se, are now served instead of being rejected by Tomcat.not_found instead of 500 for a trust mark type configured without trust-mark-subjects, and the trust marked entities listing returns an empty array. (#249)trust_mark_owners is no longer published. (#242)nimbus-extensions module adds Nimbus metadata policy operators for one_of with booleans and numbers, and value set to null. Metadata policies read through EntityStatementClaims use them. (#244)Date: 2026-10-05
trust_mark_type filter of the discovery endpoint now only counts valid trust marks, checked as in resolve. Before, any trust_marks entry of the requested type in the entity’s own Entity Configuration was enough. Resolve no longer accepts a trust mark whose type differs from the type of its trust_marks entry. (#166)trust_mark_type (OpenID Federation 1.0) are now read by the resolver and in subordinate listings. Entity configurations now write trust_mark_type in addition to id. Trust marks using the draft id claim are still accepted. An invalid trust mark entry is skipped and logged instead of dropping all trust marks of the entity. (#179)ec_location now follows OpenID Federation Entity Configuration Hosting 1.0. Only https URLs and data URLs are accepted, and other values fail at configuration load instead of being dropped. The new federation.allow-http-ec-location setting allows http for local tests. Configured data URLs are now issued, relative values work for filtered subordinate listings, and the resolver rejects Subordinate Statements with a disallowed ec_location. Warnings are logged when ec_location is issued for an Intermediate Entity or marked as critical. (#182)trust_mark_issuers claim is now published and read as defined by OpenID Federation 1.0. (#183)trust_mark_owners now require a valid delegation from the owner. A trust mark that fails the check is dropped instead of failing the resolve. (#184)crit or metadata_policy_crit lists claims or operators it does not support. (#189)trust_mark_issuers now means that any issuer is accepted, as required by OpenID Federation 1.0. (#192)expired based on the expiry of the trust mark itself. (#193)invalid_request instead of 500 for a trust mark that cannot be parsed. (#196)allowed_entity_types constraint now removes disallowed entity types from the resolved metadata instead of rejecting the trust chain, and an empty list allows only federation_entity. (#197)value set to null, subset_of giving an empty array, merging of one_of, and scope handled as a list of values. (#198)invalid_metadata with HTTP 400 instead of 500, and entities without metadata no longer cause an error. (#199)trust_anchor parameters now use the first Trust Anchor the resolver is configured for. (#200)entity_type, and the parameter may be given more than once. (#201)authority_hints that point back to each other or to a superior without a subordinate statement for the entity. (#202)authority_hints of the entity it issues a statement about. (#204)kid header, or with a kid that does not match the verifying keys, are now rejected. (#205)application/entity-statement+jwt. (#207)jwks, authority_hints and crit from the subject’s Entity Configuration. (#209)invalid_request when trust_mark_type or sub is missing. (#212)invalid for trust marks without the typ header trust-mark+jwt. (#214)sub now give 400 invalid_request. (#215)trust_marked=false and intermediate=false no longer filter the subordinate listing. (#216)trust_marked or intermediate value other than true or false now give 400 invalid_request. (#217)intermediate filter of the subordinate listing now counts every subordinate with a fetch endpoint as an intermediate, also when it has no list endpoint. (#218)entity_type or intermediate, since their types are unknown. (#219)null, or federation_entity in allowed_entity_types. (#221)not_found error instead of an empty 404. (#222)/ are now served at the well-known path and their endpoints without a double slash. (#225)crit claim of signed statements now only lists extension claims that are present in the statement, and is left out when there are none. (#226)dead-nodes actuator endpoint meanwhile. (#227)kid-algorithm, metadata policies and the resolver response duration. JSON resolver configuration now reads resolve-response-duration, as documented, and still accepts resolver-response-duration. (#229)authority_hints and used the entity type relying_party instead of openid_relying_party.Date: 2026-09-30
crit, metadata_policy_crit and authority_hints values are no longer written as empty arrays in issued statements, as required by OpenID Federation 1.0.crit when it is set for the entity.Date: 2026-09-29
Date: 2026-09-18
entity_type query parameters correctly — repeated entity_type values now return the union of matching Entity Types, as required by OpenID Federation 1.0 Section 8.2.1, instead of only the first valueDate: 2026-09-17
Date: 2026-09-08
/trust_mark_status is now served over POST with parameters encoded as application/x-www-form-urlencoded, as required by section 8.4.1 of OpenID Federation 1.0. GET with query parameters is still accepted for backwards compatibilityFederationClient now sends Trust Mark Status requests over POSTGET requests for endpoints that are specified as GET onlyDate: 2026-09-04
StepRecoveryStrategy / ScheduledStepRecoveryStrategy retry mechanism and the step-retry-time resolver propertyfederation.service.scheduling.resolver-reload-rate) changed from PT60M to PT10MDate: 2026-08-18
NullPointerException in subordinate listing filters when an entity configuration has no trust_marks or no federation_entity metadataNullPointerException in trust mark collection when the trust anchor has no trust_mark_owners or a chain statement has no trust_marksNullPointerException in key configuration when a key mapping (federation/hosted) is not configured/discovery is now served under the entity identifier for entities without a virtual entity id, and matching ignores query parametersDate: 2026-06-18
/jwks response — keys registered under both an alias and their key ID were previously returned twicename claim to /jwks JWT response containing the configured alias names for federation and hosted keysJWKSRouter is now active when virtual entity routing is enabled/jwks endpoint across all test suitesDate: 2026-06-16
Date: 2026-05-22
Date: 2026-05-22
Date: 2026-05-21
Date: 2026-05-20
Date: 2026-04-13
Date: 2026-04-13
nodeRadius to exported node dataDate: 2026-04-13
/actuator/dead-nodes) to list dead nodes in the federationMeasured with Redis, 1000 requests per scenario. (Redis 7.4.7 via Testcontainers, Apple M2 MacBook Air, 8-core, 24 GB RAM)
Test Timings:
| Test | Requests | Total (s) | RPS |
|---|---|---|---|
| Resolve without cache (12.87 KB) | 1000 | 4.966 | 201.4 |
| Entity Configuration without cache (3.36 KB) | 1000 | 3.489 | 286.6 |
| Trust mark status without cache (2.58 KB) | 1000 | 1.778 | 562.4 |
| Trust mark without cache (0.30 KB) | 1000 | 1.427 | 700.8 |
| Subordinate fetch without cache (0.69 KB) | 1000 | 0.512 | 1953.1 |
| Entity Configuration with cache (3.36 KB) | 1000 | 0.204 | 4902.0 |
| Trust mark status with cache (2.58 KB) | 1000 | 0.196 | 5102.0 |
| Resolve with cache (12.87 KB) | 1000 | 0.196 | 5102.0 |
| Subordinate fetch with cache (0.69 KB) | 1000 | 0.190 | 5263.2 |
| Trust mark with cache (0.30 KB) | 1000 | 0.170 | 5882.4 |
Cache Performance Gain:
| Scenario | Payload | Cached RPS | No-cache RPS | Speedup | Cached Mbit/s | No-cache Mbit/s |
|---|---|---|---|---|---|---|
| Entity Configuration | 3.36 KB | 4902.0 | 286.6 | 17.1x | 134.927 | 7.889 |
| Resolve | 12.87 KB | 5102.0 | 201.4 | 25.3x | 537.913 | 21.231 |
| Subordinate fetch | 0.69 KB | 5263.2 | 1953.1 | 2.7x | 29.750 | 11.040 |
| Trust mark | 0.30 KB | 5882.4 | 700.8 | 8.4x | 14.456 | 1.722 |
| Trust mark status | 2.58 KB | 5102.0 | 562.4 | 9.1x | 107.833 | 11.887 |
Date: 2026-04-13
ModuleResponseCache interface with in-memory and Redis implementations to cache module responses per entity IDRedisEntityRecordIndex for Redis-backed entity record lookupsGrafanaExportCacheWarmer to pre-warm the export cache on startupFederationBaseRouter and related routing infrastructure to support virtual entity ID dispatchCompositeRecordSource and LocalRecordSource to compose entity record lookups across modulesDate: 2026-04-02
exp claimMeasured with Redis, 1000 requests per scenario. (Redis 7.4.7 via Testcontainers, Apple M2 MacBook Air, 8-core, 24 GB RAM)
Test Timings:
| Test | Requests | Total (s) | RPS |
|---|---|---|---|
| Resolve without cache (12.87 KB) | 1000 | 5.170 | 193.4 |
| Entity Configuration without cache (3.36 KB) | 1000 | 4.257 | 234.9 |
| Trust mark status without cache (2.58 KB) | 1000 | 1.921 | 520.6 |
| Trust mark without cache (0.30 KB) | 1000 | 1.640 | 609.8 |
| Subordinate fetch without cache (0.69 KB) | 1000 | 0.638 | 1567.4 |
| Entity Configuration with cache (3.36 KB) | 1000 | 2.002 | 499.5 |
| Resolve with cache (12.87 KB) | 1000 | 0.424 | 2358.5 |
| Trust mark status with cache (2.58 KB) | 1000 | 0.318 | 3144.7 |
| Subordinate fetch with cache (0.69 KB) | 1000 | 0.317 | 3154.6 |
| Trust mark with cache (0.30 KB) | 1000 | 0.287 | 3484.3 |
Cache Performance Gain:
| Scenario | Payload | Cached RPS | No-cache RPS | Speedup | Cached Mbit/s | No-cache Mbit/s |
|---|---|---|---|---|---|---|
| Entity Configuration | 3.36 KB | 499.5 | 234.9 | 2.1x | 13.749 | 6.466 |
| Resolve | 12.87 KB | 2358.5 | 193.4 | 12.2x | 248.658 | 20.393 |
| Subordinate fetch | 0.69 KB | 3154.6 | 1567.4 | 2.0x | 17.831 | 8.860 |
| Trust mark | 0.30 KB | 3484.3 | 609.8 | 5.7x | 8.563 | 1.499 |
| Trust mark status | 2.58 KB | 3144.7 | 520.6 | 6.0x | 66.463 | 11.002 |
Date: 2026-04-02
exp claimMeasured with Redis, 1000 requests per scenario. (Redis 7.4.7 via Testcontainers, Apple M2 MacBook Air, 8-core, 24 GB RAM)
Test Timings:
| Test | Requests | Total (s) | RPS |
|---|---|---|---|
| Resolve without cache (12.87 KB) | 1000 | 10.100 | 99.0 |
| Entity Configuration without cache (3.36 KB) | 1000 | 9.196 | 108.7 |
| Trust mark status without cache (2.58 KB) | 1000 | 4.191 | 238.6 |
| Trust mark without cache (0.30 KB) | 1000 | 3.757 | 266.2 |
| Entity Configuration with cache (3.36 KB) | 1000 | 3.222 | 310.4 |
| Subordinate fetch without cache (0.69 KB) | 1000 | 1.324 | 755.3 |
| Trust mark status with cache (2.58 KB) | 1000 | 0.965 | 1036.3 |
| Trust mark with cache (0.30 KB) | 1000 | 0.750 | 1333.3 |
| Subordinate fetch with cache (0.69 KB) | 1000 | 0.677 | 1477.1 |
| Resolve with cache (12.87 KB) | 1000 | 0.541 | 1848.4 |
| Total | 34.723 |
Cache Performance Gain:
| Scenario | Payload | Cached RPS | No-cache RPS | Speedup | Cached Mbit/s | No-cache Mbit/s |
|---|---|---|---|---|---|---|
| Entity Configuration | 3.36 KB | 310.4 | 108.7 | 2.9x | 8.543 | 2.993 |
| Resolve | 12.87 KB | 1848.4 | 99.0 | 18.7x | 194.882 | 10.439 |
| Subordinate fetch | 0.69 KB | 1477.1 | 755.3 | 2.0x | 8.349 | 4.269 |
| Trust mark | 0.30 KB | 1333.3 | 266.2 | 5.0x | 3.277 | 0.654 |
| Trust mark status | 2.58 KB | 1036.3 | 238.6 | 4.3x | 21.902 | 5.043 |
Date: 2026-04-02
Date: 2026-04-02
CacheSnapshotVersionLookup refactor)Date: 2026-04-01
Measured with Redis, 10000 parallel requests per scenario. (Federation with over 500 nodes, Apple M2 MacBook Air, 8-core, 24 GB RAM)
| Scenario | Payload | Cached RPS | No-cache RPS | Speedup | Cached Mbit/s | No-cache Mbit/s |
|---|---|---|---|---|---|---|
| Entity Configuration | 3.36 KB | 2645.5 | 280.3 | 9.4x | 72.82 | 7.72 |
| Resolve | 12.87 KB | 2717.4 | 209.0 | 13.0x | 286.50 | 22.04 |
| Subordinate fetch | 0.69 KB | 3076.9 | 1908.4 | 1.6x | 17.39 | 10.79 |
| Trust mark | 0.30 KB | 3125.0 | 606.4 | 5.2x | 7.68 | 1.49 |
| Trust mark status | 2.58 KB | 1712.3 | 586.5 | 2.9x | 36.19 | 12.40 |
Date: 2026-03-31
Date: 2026-03-31
SubordinateFetchCache interface with in-memory and Redis implementations; TrustAnchorRouter now caches /fetch responses and performs cache lookup before creating the TrustAnchor instanceTrustMarkCache interface with in-memory and Redis implementations; TrustMarkIssuerRouter now caches /trust_mark responses and performs cache lookup before creating the TrustMarkIssuer instanceTrustMarkIssuerRouter and ResolverRouter to defer property resolution and factory creation until after a cache miss, avoiding unnecessary work on cache hitsCachedRecordSource to reduce redundant lookups against the backing cache storeMeasured with Redis, 10000 parallel requests per scenario. (Small federation test, Apple M2 MacBook Air, 8-core, 24 GB RAM)
| Scenario | Payload | Cached RPS | No-cache RPS | Speedup | Cached Mbit/s | No-cache Mbit/s |
|---|---|---|---|---|---|---|
| Entity Configuration | 3.36 KB | 1633.5 | 284.6 | 5.7x | 44.96 | 7.83 |
| Resolve | 12.87 KB | 3235.2 | 595.7 | 5.4x | 341.09 | 62.81 |
| Subordinate fetch | 0.69 KB | 3944.8 | 1563.7 | 2.5x | 22.30 | 8.84 |
| Trust mark | 0.30 KB | 4557.9 | 453.8 | 10.0x | 11.20 | 1.12 |
| Trust mark status | 2.58 KB | 3647.0 | 607.9 | 6.0x | 77.08 | 12.85 |
Date: 2026-03-31
ResolverResponseCache and TrustMarkStatusCache interfaces with in-memory and Redis implementations, replacing the previous TrustMarkStatusStoreCacheStateManager; replaced with RegistryStateTrigger and ResolverStateTrigger for cleaner state managementScrapedEntityLookup and ScrapedTrustMarkInfo to carry all available scraped data through the cache layer/resolve endpoint via RedisResolverResponseCache and InMemoryResolverResponseCacheVersionedInMemoryCache and VersionedCacheLayer to align with the new cache interfacesCacheTestCases integration tests covering both in-memory and Redis cache configurationsDate: 2026-03-28
Date: 2026-03-16
KeyProperty.mapping now accepts a list of strings instead of a single string, allowing a key to be registered under multiple mappings simultaneouslyDate: 2026-03-16
Date: 2026-03-16
TrustMarkIssuer now throws a descriptive NotFoundException when a requested trust mark type is not configured, instead of a generic NoSuchElementExceptionDate: 2026-03-06
toString(true) directly instead of going through the reference serializerDate: 2026-02-20
KeyRegistry. If an unknown key is referenced, startup fails with a descriptive error message.Date: 2026-02-19
Date: 2026-02-18
EntityRecordDeserializer for proper deserialization of entity records, with JWKS kid-reference support and fallback to the default key from KeyRegistry when no JWKS is presentTrustMarkDelegation validation: the delegation type header mismatch now correctly throws an exception (missing throw keyword)TrustMarkDelegation validation: changed validated claim from id to trust_mark_type to align with the OpenID Federation 1.0 specificationTrustMarkDelegation validation for the alg field in the JWT headerTrustMarkDelegation validation that iat must be before exp when expiration is present/trust_mark_status endpoint now returns correct content type application/trust-mark-status-response+jwtEntityRecordDeserializer and removed redundant exclusion strategyDate: 2026-01-30
Date: 2026-01-30
Date: 2026-01-30
Date: 2026-01-29
Date: 2026-01-29
Date: 2026-01-27
Date: 2026-01-27
Date: 2026-01-27
Date: 2026-01-26
Date: 2026-01-26
Copyright © 2025-2026, Myndigheten för digital förvaltning - Swedish Agency for Digital Government (DIGG). Licensed under version 2.0 of the Apache License.