Skip to content

fix: scope SAT cookie to current subdomain, not broad .osaas.io domain (closes #33)#36

Open
LucasMaupin wants to merge 1 commit into
mainfrom
fix/issue-33-sat-cookie-domain-scope
Open

fix: scope SAT cookie to current subdomain, not broad .osaas.io domain (closes #33)#36
LucasMaupin wants to merge 1 commit into
mainfrom
fix/issue-33-sat-cookie-domain-scope

Conversation

@LucasMaupin

Copy link
Copy Markdown
Collaborator

Summary

  • Removes the explicit domain=.osaas.io attribute from the SAT bearer token cookie set in authenticateWithOpenLive() in src/lib/sat.ts.
  • Without an explicit domain attribute, browsers scope the cookie to document.location.hostname (e.g. open-live-studio.tenant.osaas.io), preventing any other co-tenant application on *.osaas.io from reading the token via document.cookie.
  • isOnOsc() is unchanged — it still detects the OSC environment by checking that the hostname ends with .osaas.io.
  • Updated JSDoc and inline comments to reflect the tighter cookie scope.

Closes #33

closes #33)

Remove the explicit `domain=.osaas.io` attribute from the SAT cookie set in
authenticateWithOpenLive(). Without an explicit domain, browsers scope the cookie
to the exact hostname (e.g. open-live-studio.tenant.osaas.io), preventing other
co-tenant applications on *.osaas.io from reading the bearer token.

isOnOsc() is unchanged — it still detects OSC by checking .osaas.io suffix.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[SECURITY][MEDIUM] SAT bearer token cookie scoped to overly broad .osaas.io domain — cross-tenant token exposure

1 participant