Repository navigation
Conversation
|
You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool. What Enabling Code Scanning Means:
For more information about GitHub Code Scanning, check out the documentation. |
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.
Gate private S3 static content before CloudFront cache delivery using one Lambda@Edge viewer-request handler. A local generator produces a deployment-specific ZIP containing bundled JavaScript, configuration, an ES256 signing key/JWKS and AES-256-GCM session keys. Sessions default to 43,200 seconds, configurable in seconds. Optional
enable_readable_id_token_cookie(defaultfalse) publishes the full validated provider JWT in a separate JavaScript-readable__Host-soca_id_tokencookie, capped by token/session expiry, cleared on logout and stripped from origin requests. The encrypted session remains HttpOnly and controls access. Normal authenticated content requests use local cryptography; sign-in contacts only the trusted identity provider. No runtime AWS SDK, KMS, Secrets Manager or database.Includes reusable Terraform and CloudFormation function deployment, a private S3/OAC/CloudFront Terraform example, an HTTPS demo container with a clearly labelled identity-provider simulator, CI, Dependabot, CodeQL and an assessment of all 34 SOCA requirements. Generated secret-bearing packages stay out of Git and public CI artefacts.
Validation: 67 tests pass locally and inside the Podman demo container with external networking disabled. Tests cover code/PKCE/private_key_jwt, ID-token/admission failures, browser binding, cookie tampering, expiry, local logout, readable JWT opt-in/verification/expiry/size/cleanup, staged key overlap, real TLS transport and the executable standalone ZIP. Example package is about 32 KB. Terraform formatting/validation and cfn-lint pass; npm audit reports no vulnerabilities. Real HTTPS RESOAuth discovery succeeded.
MVP limits: one issuer and ES256; stateless operation cannot guarantee atomic transaction consumption across edge replicas or individually revoke copied session cookies. Automated rotation, candidate-only operator testing/enforced activation, real AWS deployment, live-provider browser sign-in and OIDC conformance remain unverified or planned. Production activation is manual; see docs/requirements.md and docs/security.md.