Answer: Send the user to the Origin user-confirmation URL with installation_id or client_id, redirect_uri, and state; on confirmation Origin redirects to your callback with a confirmation_receipt JWT and state, which you must verify before reading its user claims. Verify the receipt by resolving the signing key from the JWKS by the kid header, requiring alg EdDSA and typ origin-user-confirmation-receipt+jwt, validating signature, iss, aud, and exp, and matching the signed state (and installation_id when applicable). Status: Confirmed Entry: tool/cursor/integrations/confirm-user-identity Revision: 2 Digest: sha256:3a4adb63d4e8f8ae (changes whenever the content changes) Timeline: Created: 2026-11-14T12:31:25Z Last changed: 2026-11-20T12:35:10Z (state claim: — → ORIGINAL_VALUE) Last verified: 2026-11-20T12:35:10Z Next check: 2026-11-21T12:35:10Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of confirmation URL | https://cursor.com/codebase/apps/user-confirmation | [1] | 2026-11-20 callback example | https://app.example.com/origin/confirm?confirmation_receipt=RECEIPT_JWT&state=RANDOM_ANTI_FORGERY_VALUE | [1] | 2026-11-20 receipt type | origin-user-confirmation-receipt+jwt | [1] | 2026-11-20 required algorithm | EdDSA | [1] | 2026-11-20 receipt expiry | five minutes | [1] | 2026-11-20 user ID claim | user_01... | [1] | 2026-11-20 state claim | ORIGINAL_VALUE | [1] | 2026-11-20 Sources: [1] Anysphere. "cursor.com/docs/api/origin/acting-as-users.md". https://cursor.com/docs/api/origin/acting-as-users.md Role: primary. Accessed: 2026-11-20T12:35:10Z Quote: "https://cursor.com/codebase/apps/user-confirmation" (Supports: confirmation URL) Quote: "https://app.example.com/origin/confirm?confirmation_receipt=RECEIPT_JWT&state=RANDOM_ANTI_FORGERY_VALUE" (Supports: callback example) Quote: ""typ": "origin-user-confirmation-receipt+jwt"" (Supports: receipt type) Quote: "Require `alg: EdDSA` and `typ: origin-user-confirmation-receipt+jwt`" (Supports: required algorithm) Quote: "Receipts expire five minutes after issuance." (Supports: receipt expiry) Quote: ""sub": "user_01..."" (Supports: user ID claim) Quote: ""state": "ORIGINAL_VALUE"" (Supports: state claim) Snapshot SHA-256: 24ca0008ba56cb6bfd5b961a20c89f4a856a122325428c0d7e6c01c0fc3d5a90 (captured 2026-11-19T12:29:58Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-19T12:29:56Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T12:35:10Z. No independent second source is configured for this entry Last successful check: 2026-11-20T12:35:10Z Last attempt: 2026-11-20T12:35:10Z Notes and limitations: Extracted automatically from a single official source (section "User confirmation"). Related: https://latestn.com/tool/cursor/integrations/connect-bitbucket-account How do I connect my Bitbucket account to Cursor? https://latestn.com/tool/cursor/integrations/connect-bitbucket-repository How do I connect a Bitbucket repository to a Cursor agent? https://latestn.com/tool/cursor/integrations/connect-github How do I connect GitHub to Cursor for Cloud Agents? https://latestn.com/tool/cursor/integrations/cloud-agents-mcp-support Does Cursor Cloud Agents support MCP servers? https://latestn.com/tool/cursor/integrations/cloud-mcp-tools-permissions What MCP tools can Cursor Cloud Agents access and what permissions do they have? https://latestn.com/tool/cursor/integrations/configure-otel-export How do I configure Cursor Agent SDK to send OpenTelemetry traces, metrics, and logs to an OTLP collector? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-20T12:35:10Z | changed | state claim: — → ORIGINAL_VALUE | [1] 2026-11-20T12:35:10Z | changed | required algorithm: — → EdDSA | [1] 2026-11-20T12:35:10Z | changed | algorithm: EdDSA → — | [1] 2026-11-14T12:31:25Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/cursor/integrations/confirm-user-identity/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/cursor/integrations/confirm-user-identity POST: https://latestn.com/dispute/tool/cursor/integrations/confirm-user-identity with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/cursor/integrations/confirm-user-identity?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I confirm a user's Cursor identity and handle the callback in Origin? Revision 2, last verified 2026-11-20T12:35:10Z. https://latestn.com/tool/cursor/integrations/confirm-user-identity (accessed 2026-11-21T09:56:40Z). @misc{LatestN_tool_cursor_integrations_confirm_user_identity_r2, title = {How do I confirm a user's Cursor identity and handle the callback in Origin?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/cursor/integrations/confirm-user-identity}}, note = {Revision 2; digest sha256:3a4adb63d4e8f8ae; last verified 2026-11-20T12:35:10Z; accessed 2026-11-21T09:56:40Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/cursor/integrations/confirm-user-identity