Repository navigation
fix(security): eliminate ticket signing dev fallback and harden cloud deployment guards - #45
Merged
Merged
Conversation
…d harden cloud deployment guards
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…on review, and owner actions
…tion reconciliation
…e access layer audit
…xposure provisioning runbook
…reation instructions
…cs suite and remove 76 obsolete reports
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.
Summary
lib/services/tickets.jsto fail closed (503not_configured) in Production or Vercel ifTICKET_SECRET/SESSION_SECRETis missing or < 32 characters, eliminating any fallback to dev secret.lib/dev-personas.jsto fail closed against any ambiguous deployed environment (VERCEL,AWS_LAMBDA_FUNCTION_NAME, etc.) whenVERCEL_ENV !== 'preview'.test/production-readiness.test.js.