From 2321e743339d592a6ca8dafe81c570e5447f4db1 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Mon, 17 Aug 2026 16:26:34 +0000 Subject: [PATCH] Version Packages --- .changeset/tough-donuts-repair.md | 18 ------------------ CHANGELOG.md | 19 +++++++++++++++++++ Directory.Packages.props | 2 +- package.json | 2 +- 4 files changed, 21 insertions(+), 20 deletions(-) delete mode 100644 .changeset/tough-donuts-repair.md diff --git a/.changeset/tough-donuts-repair.md b/.changeset/tough-donuts-repair.md deleted file mode 100644 index a0c5bf1..0000000 --- a/.changeset/tough-donuts-repair.md +++ /dev/null @@ -1,18 +0,0 @@ ---- -"@monocloud/authentication-api": patch ---- - -- Infrastructure failures during introspection (discovery, transport, non-2xx responses, malformed - JSON, client auth) and exceptions from consumer event handlers on the opaque path now raise - `AuthenticationFailed` with the real exception and rethrow (→ 500) instead of failing with a - misleading 401 `invalid_token`. Token verdicts (`active:false`, certificate binding) still produce - a 401. To restore the old behavior, handle `OnAuthenticationFailed` and set a `Result`. -- A failing introspection-cache write no longer fails an otherwise-successful authentication. -- A space-delimited `scope` claim in a locally validated JWT is split into one claim per scope, - matching the introspection path, so `RequireClaim("scope", ...)` behaves identically on both paths. -- Claim normalization preserves the validated identity's type (Wilson 8's - `CaseSensitiveClaimsIdentity` on .NET 9+) instead of rebuilding a case-insensitive `ClaimsIdentity`. -- The in-flight introspection de-duplication map is keyed by scheme + token, so concurrent - introspections of the same token under different schemes no longer share a result. -- Removed `JwtAssertion.AssertionCacheExpiry` (compile-breaking if set): it was never honored — a - fresh assertion (new `jti`) is generated for every introspection request. diff --git a/CHANGELOG.md b/CHANGELOG.md index 0abc095..d12635b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,24 @@ # @monocloud/authentication-api +## 0.1.4 + +### Patch Changes + +- 09ca43f: - Infrastructure failures during introspection (discovery, transport, non-2xx responses, malformed + JSON, client auth) and exceptions from consumer event handlers on the opaque path now raise + `AuthenticationFailed` with the real exception and rethrow (→ 500) instead of failing with a + misleading 401 `invalid_token`. Token verdicts (`active:false`, certificate binding) still produce + a 401. To restore the old behavior, handle `OnAuthenticationFailed` and set a `Result`. + - A failing introspection-cache write no longer fails an otherwise-successful authentication. + - A space-delimited `scope` claim in a locally validated JWT is split into one claim per scope, + matching the introspection path, so `RequireClaim("scope", ...)` behaves identically on both paths. + - Claim normalization preserves the validated identity's type (Wilson 8's + `CaseSensitiveClaimsIdentity` on .NET 9+) instead of rebuilding a case-insensitive `ClaimsIdentity`. + - The in-flight introspection de-duplication map is keyed by scheme + token, so concurrent + introspections of the same token under different schemes no longer share a result. + - Removed `JwtAssertion.AssertionCacheExpiry` (compile-breaking if set): it was never honored — a + fresh assertion (new `jti`) is generated for every introspection request. + ## 0.1.3 ### Patch Changes diff --git a/Directory.Packages.props b/Directory.Packages.props index 9f0fc99..bcceeab 100644 --- a/Directory.Packages.props +++ b/Directory.Packages.props @@ -3,7 +3,7 @@ 14.0 enable true - 0.1.3 + 0.1.4 0.0.1 0.0.1 MonoCloud diff --git a/package.json b/package.json index 7de9004..35d4ea8 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "@monocloud/authentication-api", - "version": "0.1.3", + "version": "0.1.4", "private": true, "scripts": { "changeset": "changeset",