From fe8133b21c81a9ba09e3425ed53d5d79b21fda72 Mon Sep 17 00:00:00 2001 From: William Mantly Date: Thu, 23 Jul 2026 16:10:20 -0400 Subject: [PATCH] Release 1.3.6: bump sso-manager-node to v1.3.2 Fixes the OAuth-client-API client_id serialization bug that broke this stack's bootstrap (rotate -> 500 -> 'bootstrap failed'). See CHANGELOG. Co-Authored-By: Claude Opus 4.8 --- CHANGELOG.md | 10 ++++++++++ sso-manager-node | 2 +- 2 files changed, 11 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index abc1ab5..92da611 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -10,6 +10,16 @@ for what changed inside the apps it composes. ## [Unreleased] +## [1.3.6] - 2026-07-23 + +### Bumped +- sso-manager-node -> [v1.3.2](https://github.com/theta42/sso-manager-node/releases/tag/v1.3.2) + +sso-manager-node 1.3.2: + +### Fixed +- **OAuth client management API returned `client_id: undefined` on every GET**, which broke this stack's bootstrap: it lists the OAuth clients and rotates by the returned `client_id`, so it called `/api/oauth/client/undefined/rotate` and got a 500 — aborting `setup.sh` with `bootstrap failed` whenever `proxy-secrets.js` had no usable secret (e.g. a fresh/rotated deployment). The ORM's `toJSON()` was stripping the mapped `client_id`/`scopes`/… fields; `OAuthClient.get()` now emits them explicitly (and omits `client_secret_hash`). Unknown client ids now 404 instead of 500. + ## [1.3.5] - 2026-07-23 ### Added diff --git a/sso-manager-node b/sso-manager-node index 3babf18..d9a3cb6 160000 --- a/sso-manager-node +++ b/sso-manager-node @@ -1 +1 @@ -Subproject commit 3babf18fe4eb291e66bcb280d6adfd543472e5cb +Subproject commit d9a3cb604483e11de59f35488e03c6500c5a240e