Chore/Upgrade packages #41
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
IDisposable
force-pushed
the
chore/packages
branch
from
4d6c80a to
353ae76
Compare
IDisposable
force-pushed
the
chore/packages
branch
from
e35f6c8 to
a395e93
Compare
Contributor
Author
|
Rebased. |
IDisposable
force-pushed
the
chore/packages
branch
from
a395e93 to
f35da1b
Compare
IDisposable
force-pushed
the
chore/packages
branch
3 times, most recently
from
0d457a0 to
0e77fc8
Compare
Update dockerfile for correct node version. Update package for openid-client This essentially required reconstructing the oidc.go and auth.go files following the 6.x examples. While doing that, resolved some performance problems by only validating and parsing the session-stored JWT token once in the authenticated path and inserting the resulting sub (subject) into the request object for access in the next endpoint. This greatly simplifies the parts that expect an authenticated endpoint. Added indexes for database performance. Can't get the migration to generate!
IDisposable
force-pushed
the
chore/packages
branch
from
0e77fc8 to
0a1f3af
Compare
Contributor
Author
|
@adamshiervani I can't seem to get the |
IDisposable
commented
Jan 29, 2026
| const JWKS_URL = new URL("https://www.googleapis.com/oauth2/v3/certs") | ||
| const JWKS = jose.createRemoteJWKSet(JWKS_URL); | ||
| const verificationOptions = { | ||
| //algorithms: ['RS256'], |
Contributor
Author
There was a problem hiding this comment.
The example shows S256 but really should be RS256... until I can test I can't be sure which is right.
Contributor
|
Latest dev contains Readme and DX improvements. It should be more straightforward now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Now runs on Node 22.22.0
This also required major updates to oidc.ts and auth.ts, so updated the way the JWT Token was being managed to only validate and extract ONCE per request.
Upgraded the Dockerfile to use
node:22.22.0-alpinebase imageAdded indexes to the database schema for better performance
** NEED TO GENERATE THE MIGRATION **