feat(extension): browser extension core for Chrome and Firefox#418
Open
oxr463 wants to merge 6 commits into
Open
feat(extension): browser extension core for Chrome and Firefox#418oxr463 wants to merge 6 commits into
oxr463 wants to merge 6 commits into
Conversation
- Add chrome-extension:// and moz-extension:// to CORS allowed origin patterns so the extension can make credentialed requests - Fix UserContext.getUserId() to handle JwtAuthenticationToken (set by oauth2ResourceServer for Bearer token requests) in addition to the existing UserAuthenticationToken (set by the cookie filter); the hard cast was causing a ClassCastException and 500 on all extension API calls
- Mock next/font/google in vitestSetup to fix Libre_Baskerville not-a-function error in app.test.tsx - Always render brand logo in Navbar (remove isMobile conditional that hid it on desktop); drop unused isMobile state and resize effect - Update default avatar test to assert SVG icon presence instead of stale img/src expectation
R-Sandor
reviewed
Jun 8, 2026
R-Sandor
reviewed
Jun 8, 2026
R-Sandor
requested changes
Jun 10, 2026
R-Sandor
left a comment
R-Sandor
left a comment
Collaborator
There was a problem hiding this comment.
While the sign-in seems to work for firefox, there is an issue with the auth. The bear token filter doesn't succeed when attempting to add a bookmark.
On Firefox Linux the application also doesn't persist the token (maybe?) as each time the extension is opened it requires reauthentication.
Ideally the extension should be able to maintain login in for the life of the JWT.
Please test on your end.
R-Sandor
force-pushed
the
feature/browser-extensions
branch
from
34e0791 to
ffb1aef
Compare
- Add jwtAuthenticationConverter inline in securityFilterChain so Bearer token requests produce UserAuthenticationToken directly; avoids registering a Converter bean that breaks Spring MVC startup - Remove JwtAuthenticationToken fallback from UserContext since the converter now handles Bearer token auth uniformly - Add accessToken to TokenRefreshResponse so the extension can read the JWT from the sign-in response body (httpOnly cookie is not accessible from moz-extension:// origin) - Build server image from source in docker-compose for local dev
6 tasks
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
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.
Issue number: resolves #417
Checklist
What is the current behavior?
There is no browser extension. Users must navigate to the FindFirst web app, manually enter a URL and title, and select tags to save a bookmark — interrupting their browsing flow.
The repository contained only a non-functional Firefox Manifest V2 stub and an empty Chrome directory.
What is the new behavior?
accessToken) returned in the sign-in response body and stored inbrowser.storage.local; sent asAuthorization: Beareron all API calls; session persists across popup close/open for the lifetime of the JWTsrc/) builds separate Chrome MV3 (dist/chrome/) and Firefox MV3 (dist/firefox/) artifacts via esbuildServer-side changes (this PR)
chrome-extension://*andmoz-extension://*added to allowed origin patterns so the extension can make cross-origin requestsjwtAuthenticationConverterwired intooauth2ResourceServerso Bearer token requests produceUserAuthenticationTokendirectly, makingUserContext.getUserId()work for extension API callsaccessToken(JWT) added toTokenRefreshResponsebody alongsiderefreshToken; the extension reads this from the response since thehttpOnlycookie set for web clients is not accessible from extension originsdocker-compose.ymlfor local development iterationDoes this introduce a breaking change?
Other information
Firefox manifest: Firefox MV3 uses
background.scripts(array) rather thanbackground.service_worker. The extension build produces browser-specific manifests frommanifests/manifest.firefox.jsonandmanifests/manifest.chrome.json.Docker Compose: The extension is a static build artifact loaded directly into the browser — it does not run as a container.