Document the viewer attributes OptiView Live reports on a rejected token - #867
Merged
Merged
Conversation
frankforpresident
requested review from
christopher-dolby and
jeroentempels-dolby
September 16, 2026 08:46
jeroentempels-dolby
approved these changes
Sep 16, 2026
This comment has been minimized.
This comment has been minimized.
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.
When a viewer's JWT is rejected, the OptiView Live CDN now returns an
x-optiview-viewerheader describing how it sees that viewer: the country, region, DMA code and device type it resolved, which are exactly the values the token'soptiviewgeo and device restrictions are evaluated against. Comparing them against the issued token is what makes a rejected viewer debuggable, which an HTTP 403 on its own is not.Adds a "Troubleshooting rejected viewers" section to the Live token-based security page, covering the attribute table, a worked 403 example, and the three caveats a reader would otherwise trip over: the values describe the viewer and not the rejection (every token-caused rejection reports the same attributes, so the header never says which restriction failed), only attributes the CDN could resolve are listed, and the header is exposed for cross-origin reads so browser players can read it.
Implemented in the cdn repo (PR #318, OLIVE-717); docs task is OLIVE-795.
Two deliberate omissions: the internal numeric reason code header is not documented (it is absent from these docs today and intentionally non-obvious), and CloudFront is not mentioned since it does not report the attributes yet (OLIVE-784).
Publish after the cdn change reaches production, since the header is not live for customers before that.
npx prettier --checkon the pagenpx mdxlint(the repo's spellcheck) on the page