v2.5.1 #1767
0xJacky
announced in
Announcements
v2.5.1
#1767
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Important
If an installation ever ran NGINX UI 2.3.6 or earlier, or restored a backup from such an installation, upgrading alone does not invalidate credentials that may already have been exposed. Upgrade every instance to v2.5.1 first. In a cluster, use HTTPS for any relationship that still reports
Legacy shared secret, and confirm that each node relationship showsPaired signaturebefore rotating the shared secrets. Then:[node] Secret(NGINX_UI_NODE_SECRET) on every instance with a new, unique random value and restart the instance.[app] JwtSecret(NGINX_UI_APP_JWT_SECRET) and restart NGINX UI to invalidate previously issued JWTs.Do not manually replace
Crypto.Secret: it protects persisted encrypted data and requires a supported migration. Backup archives use one-time encryption material; rotate the credentials contained in any exposed backup instead.This hotfix includes all changes and release notes from v2.5.0.
Features
Bug Fixes
X-Node-Secretauthentication until each relationship is automatically upgraded to Ed25519 credentials.Contributors
@0xJacky
@chrstphe
@renovate
@sdjnmxd
This discussion was created from the release v2.5.1.
All reactions