Repository navigation
Conversation
Contributor
Author
|
Closing as incorporated by merged #63/#68 (#68). Rechecked exact predecessor head |
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.
The Tina preview task currently depends on a bounded personal browser session. When it expires, agents cannot independently inspect saved CMS changes or carry out authorized corrections. This proposed design uses the existing reusable Workflow/auth/authz/CMS architecture for a separate revocable service principal, a registered assertion grant and short-lived tokens.
The initial grant is limited to preview tenant234, with read/history access and a separately approved body-only update option for pages3 and6. Protected frontend viewing has its own explicit exact-origin GET/HEAD permission and audience because a CMS token cannot satisfy the current Basic gate. The proposal describes required upstream hardening, current durable-grant/revocation checks, key custody, audit and saved-history boundaries. Unsaved drafts need separate autosave/presence support.
Validation: docs-only exact head
0c872c39bcb1916d3fca6d6c8a128f0967d033fc; diff/link/boundary checks passed. Independent complete design re-review approved with no findings; report SHA256a7ea4cfccbc54f4bc119a1960904d925725563aca6cf8f28deeefb7077a2979c. No runtime code changes, credentials, keys, clients, grants or tokens were created. Implementation, mounted runtime tests, staging adoption and separate owner activation remain prerequisites; this draft authorizes none of those actions.