You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -71,6 +71,7 @@ request adding CHANGELOG notes for breaking (!) changes and possibly other secti
71
71
and a subsequent `bootstrap` would create a second, empty set of tables in the other schema.
72
72
Either remove the setting from the URL, or point it at the schema that already holds your
73
73
Polaris tables.
74
+
- Internal JWTs minted before credentials-generation binding (tokens without the `polaris-cv` claim) can no longer be used as subject tokens in token exchange; they remain valid as bearer tokens until expiry. During a rolling upgrade, an old node may still mint claim-less tokens: exchanging such a token on any already-upgraded node fails with `invalid_grant`, so clients can see intermittent exchange failures until the last old node is gone; after that, rejection is consistent.
74
75
75
76
### New Features
76
77
@@ -148,6 +149,9 @@ request adding CHANGELOG notes for breaking (!) changes and possibly other secti
148
149
directly under an allowed location, at `s3://b1/ns`, and rejected it as a custom location even
149
150
though the request asked for none. The namespace location is now compared against the
150
151
catalog's `default-base-location`, which is what it is derived from.
152
+
- Internal JWTs are bound to principal secret generation via `polaris-cv` (no secret material in the
153
+
token). Credential-generation is enforced on token exchange; bearer verify is signature and claims
154
+
only. Secrets-load failures during exchange return service unavailable.
0 commit comments