Skip to content

Epic JWT key: tolerate any PEM escaping (jwks.json was 500) #16

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
ralyodio merged 1 commit into from
Oct 12, 2026
Merged

Epic JWT key: tolerate any PEM escaping (jwks.json was 500) #16

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion apps/web/src/records.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -282,7 +282,10 @@ let jwtKey = null;
function privateKey() {
const pem = process.env.CLIENT_JWT_PRIVATE_KEY;
if (!pem) return null;
if (!jwtKey || jwtKey.pem !== pem) jwtKey = { pem, key: createPrivateKey(pem.replace(/\\n/g, '\n')) };
// The vault and the env file each add a level of escaping, so a PEM can arrive
// with literal \n, \\n, or real newlines left with a stray backslash. Base64
// never contains a backslash, so collapsing every form to a newline is safe.
if (!jwtKey || jwtKey.pem !== pem) jwtKey = { pem, key: createPrivateKey(pem.replace(/\\+(\n|n)/g, '\n')) };
return jwtKey.key;
}

Expand Down
Loading