Draft
Conversation
…erver Publish RFC 8414 and OpenID Connect discovery JSON after `next build`, with issuer wiring via SITE_ORIGIN/PUBLIC_ORIGIN and correct path layout for subpath deployments. The self-hosted server serves the same metadata dynamically plus jwks_uri. Documents intentional placeholder endpoints since the viewer UUID API is not secured by OAuth today. Co-authored-by: Aanish Bhirud <baanish@users.noreply.github.com>
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
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 |
Deploying agent-render with
|
| Latest commit: |
578bd28
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://16b40aee.agent-render.pages.dev |
| Branch Preview URL: | https://cursor-oauth-discovery-metad.agent-render.pages.dev |
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.
Summary
next build,scripts/patch-oauth-discovery.mjswrites RFC 8414 and OpenID Connect discovery JSON underout/.well-known/with the correct extensionless paths. Issuer defaults tohttps://agent-render.com; override withSITE_ORIGINorPUBLIC_ORIGINat build time. Subpath builds (NEXT_PUBLIC_BASE_PATH) use RFC 8414’s path insertion layout and placejwks.jsonunder the base path only (not at the host root).GET /.well-known/oauth-authorization-server,GET /.well-known/openid-configuration, andGET /.well-known/jwks.jsonwith issuer resolved fromPUBLIC_ORIGINor proxy headers.Notes
Documents list conventional OAuth endpoints; the static viewer and current UUID artifact API are not gated by interactive OAuth—metadata is for programmatic discovery and honest disclosure.
Verification
npm run checknpm run selfhosted:build