[codex] Add message 403 diagnostics#37
Merged
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
1 participant
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
/Messages*endpoint403failuresAuth/TokenInfoon message403s to report whether the child token advertises themessagesscope0.3.2, including the refreshedopenapi.jsonRoot Cause
Issue #36 did not reproduce as a repo-wide endpoint bug. The current implementation can read message endpoints on the verified account, so the failure mode appears to vary by child account or token capability. The fix improves diagnostics instead of changing message-call success semantics.
User Impact
Users now get a messages-specific
API_REQUEST_FAILEDpayload withfeature,requiredScope,scopePresent,tokenScopes, and alibrus auth token-infohint when Librus returns403for message endpoints.Validation
npm run validatenpm run test:integration