Skip to content

[PATCH - DO NOT MERGE] send_session_token on top of the deployed prod build - #1928

Draft
asafshen wants to merge 1 commit into
mainfrom
patch/prod-send-session-token
Draft

[PATCH - DO NOT MERGE] send_session_token on top of the deployed prod build#1928
asafshen wants to merge 1 commit into
mainfrom
patch/prod-send-session-token

Conversation

@asafshen

@asafshen asafshen commented Sep 3, 2026

Copy link
Copy Markdown
Member

Purpose

Do not merge. This PR exists only to produce a patch image for production. The change itself is already on main as #1924.

What this is

Production currently serves 532e0523a6d5d930bb664d50b93ab22a53f5e4ab (per https://api.descope.com/login/version), which predates #1924. This branch is that exact commit with #1924 cherry-picked on top and nothing else - the resulting tree is byte-identical to 0c8f85d on main, so the image is "what prod runs today, plus the send_session_token query param".

Four unrelated dependency/CI bumps sit between the deployed commit and main; deliberately not included.

Why a patch instead of a normal deploy

The send_session_token param is the last piece of a cross-repo feature - without it the hosted flow page never sets send-session-token on the web component, so the corresponding SDK work has no effect for hosted flows.

Related: https://github.com/descope/etc/issues/17811

…e flow (#1924)

Maps the new query param (or DESCOPE_SEND_SESSION_TOKEN env) to the Descope
component's sendSessionToken prop, exposing the session's validated claims
to the flow via the sessionJwtClaims context key

Co-authored-by: Claude <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.

1 participant