docs(app-config): expand cross-origin embedding cookie guidance#64
Merged
Conversation
Trello: https://trello.com/c/i1v1nLMu/228 Issue: graphistry/graphistrygpt#2849 Louie runbook: https://louieai-documentation.readthedocs.io/en/latest/admin/100_Graphistry_Iframe_Blocked.html Builds on the existing COOKIE_SECURE/COOKIE_SAMESITE block: - Document defaults (COOKIE_SECURE=false; COOKIE_SAMESITE auto-derives). - Name the cookies affected (SESSION, CSRF, JWT). - Add a DevTools verification recipe (working vs failing SameSite). - Add a sub-section for embedding-host CSP requirements with a cross-link to the Louie iframe runbook for an end-to-end example. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Clarify instructions for embedding visualizations in different origin sites.
lmeyerov
approved these changes
May 20, 2026
Contributor
lmeyerov
left a comment
There was a problem hiding this comment.
Great thank you!
(I clarified one bit as not all folks know what an origin is)
Contributor
|
Hmm readthedocs is red: https://app.readthedocs.org/projects/graphistry-admin-docs/builds/32783890/ |
lmeyerov
requested changes
May 20, 2026
Contributor
lmeyerov
left a comment
There was a problem hiding this comment.
RTD is red, looking: https://app.readthedocs.org/projects/graphistry-admin-docs/builds/32783890/
pdflatex fails with `LaTeX Error: Unicode character ↔ (U+2194)` when rendering the embedding-host checklist, breaking the Read the Docs PDF build for PR #64. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Oh, thank you @lmeyerov! |
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.
Summary
Expands the existing
Application serverscookie section under TLS Hardening with:COOKIE_SECUREdefaults tofalse;COOKIE_SAMESITEauto-derives toNonewhenCOOKIE_SECURE=true, elseLax.SESSION_COOKIE,CSRF_COOKIE,JWT_AUTH_COOKIE.SameSite=None; Secure; Failing:SameSite=Lax).frame-src/child-src) with a cross-link to the new Louie iframe runbook for the end-to-end three-way (OA2_HOST↔ Graphistry host ↔ Caddy CSP) checklist.Why
Discovery deployment hit "This content is blocked" embedding Graphistry into Louie. Root cause was misaligned cookie flags. Operators were unaware that
COOKIE_SECUREdefaults tofalse, so cross-origin cookies were gettingSameSite=Laxand the browser dropped them inside the embedded iframe.Related:
Test plan
Files changed
🤖 Generated with Claude Code