Serve OpenAI Apps domain-verification token - #21
Merged
Conversation
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.
Adds a route that serves the OpenAI Apps domain-verification token as plain text at
/.well-known/openai-apps-challengeonmcp.olostep.com, so ChatGPT can verify we control the host.The token is read from the
OPENAI_APPS_CHALLENGE_TOKENenv var, so it can be set or rotated without a code change. The route is dormant (returns 404) until the env var is set, so merging this is safe and changes nothing until the token is configured on the task.Verified locally: with the env var set the path returns 200 text/plain with the exact token; without it, 404.
To activate after merge and deploy: set
OPENAI_APPS_CHALLENGE_TOKENon the mcp ECS task, then click Verify in the OpenAI app settings.