Repository navigation
ABUSE-001A1: use reCAPTCHA Enterprise for browser App Check - #160
Merged
Merged
Conversation
✅ Deploy Preview for luminous-fox-7c393f ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Jul 13, 2026
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
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.
Closes #159
Outcome
The browser now constructs Firebase App Check with
ReCaptchaEnterpriseProvideron an ordinary production page when the public site-key variable is configured. The legacy v3 provider is absent. Local/test runtimes, initial capability callback URLs, missing-key behavior, token auto-refresh, Analytics shutdown, and fixed redacted diagnostics are preserved.This is a source/test correction only. It does not create a key, configure allowed domains, set a protected variable, enable callable enforcement, publish the website or Firebase, or prove live attestation.
Officer handoff
Officer impact: No current officer screen or procedure changes. This prepares the correct browser provider for a later owner-approved protected release.
Officer documentation: None — there is no new officer action and no live behavior after this source-only slice. The root security and operations records were updated to keep future owner/provider/deployment work explicit.
Deployment evidence: Exact-head CI run
29259142366passed frontend, Functions, and Rules at14a333bdbf5d09b9dffc34339150fcb4497ec330. Netlify deploy preview6a54f97f7e026c000828d663is ready; that is not a production publication. No website production, Firebase, provider, key, enforcement, token exchange, or live behavior is configured or proven. Protected release29254280177previously failed closed before checkout/build because the site-key variable was absent; nothing was published.Verification
Node
v20.20.2:29259142366: frontend, Functions, and Rules passed at the exact headExact source commit:
14a333bdbf5d09b9dffc34339150fcb4497ec330Exact staged diff hash reviewed:
525928f78fa8ade111b3317190b57db1f515aed1Boundary
Changed only:
src/services/firebase/FirebaseResources.tssrc/services/firebase/FirebaseResources.test.tsSECURITY.md,OPERATIONS_RUNBOOK.md,GITHUB_ISSUES.md, andGITHUB_ISSUE_SLICES.mdExcluded workflows, environment files, package/lockfiles, Functions, Rules, provider settings, keys, enforcement, officer procedures, and production data.