Repository navigation
fix: enforce token checks in gateway and edge examples and fix IaC configs - #6
Open
jhickmanit wants to merge 2 commits into
Open
jhickmanit wants to merge 2 commits into
jhickmanit wants to merge 2 commits into
Conversation
|
Important
This repository does not receive automatic reviews because it has fewer than 10 stars. ⚙️ Run configuration
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Signed-off-by: jhickmanit <jeff.hickman@ory.com>
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.
Corrects the API gateway, edge token validation, IaC, feature flag, and self-hosted infrastructure integrations so their configuration runs and validates Ory tokens correctly.
Changes
kong.yamlputs the JWKS public key inrsa_public_key, which the OSSjwtplugin requires because it does not fetch JWKS.Authorizationheader.nbfand setsX-User-Id.aliasHeadersStrategy=delete, and the Kubernetes manifest gives the matching Helm argument, so a client-sentX_User_Idcan't reach the backend asX-User-Id.X-User-Metadatais JSON with non-ASCII escaped.kid, and enforcesiss,aud,exp, andnbf.npm run devworks without a prior build.tier,groups,organization), and its wrapper forwards session tokens as well as cookies.ory.toSession().ory/ory ~> 26.3and use only real provider arguments. Actions are created per enabled authentication method. Stripe uses an ignored response after identity persistence, the URLs match the companion handlers, and Segment and Splunk have separate body templates. They ship the Jsonnet files they reference, and the README documents the import ID formats and which API key each resource needs.OTEL_RESOURCE_ATTRIBUTESis merged, butservice.nameanddeployment.environment.namecome from Ory'stracingconfig.Deployment notes
Validation
nbf, wrong issuer,alg: none, HS256, and query-string tokens are rejected. Forged headers are replaced.X-Forwarded-Urispoofing, and dot-segment traversal. A mock Ory run also covered Unicode profiles.terraform init,fmt -check, andvalidatewith Terraform 1.16.5 and ory/ory 26.3.6. Changed Jsonnet bodies pass null/missing/populated payload and handler-shape checks. No infrastructure was applied.