# US 2026/0074907 A1 · User authentication techniques across applications on a user device > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 2026/0074907 A1 - Document ID: US20260074907A1 - Status: Published application - Kind: A1 - Application number: 19/390,215 - Filed: 2025-11-14 - Published: 2026-03-12 - Earliest claimed: 2021-04-23 - Assignees: Circle Internet Group, Inc. - Applicants: Circle Internet Group, Inc. - Inventors: Itay DUVDEVANI; Roy Shifroni UDASSIN; Sona RATHOD; Oliver Sam COLLINS; Jun SUN; Mark Blelock ATHERTON; Cihad OGE; Asim Viladi Oglu MANIZADA; Feixiong ZHANG; Yuhan GUO; Huapeng ZHOU; Vincent Christian Daniel MAUGE; Kyle Steven NEKRITZ; Parvi KAUSTUBHI; Sanjay SANE; Shuo SHEN; Kawin PRAKOBKIT; Shivram Vaman KHANDEPARKER; Vignesh RAGHURAMAN - Web page: https://patentgrep.com/patent/US20260074907A1 ## CPC - H04L 9/3221: {interactive zero-knowledge proofs} - G06F 16/955: using information identifiers, e.g. uniform resource locators [URL] - H04L 9/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates} - H04L 9/0891: {Revocation or update of secret information, e.g. encryption key update or rekeying} - H04L 9/3213: {using tickets or tokens, e.g. Kerberos (network architectures or network communication protocols for entities authentication using tickets in a packet data network H04L63/0807)} - H04L 9/3218: {using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs} - H04L 9/3271: {using challenge-response} - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) ## Abstract According to examples, a system for enabling user authentication may include a processor and a memory storing instructions. The processor, when executing the instructions, may cause the system to receive user login credentials and initiate a user authentication process by receiving a challenge configured using an attribute of a system including the processor. The processor executes further instructions to determine the attribute value and to derive a zero-knowledge proof in response to the challenge. The zero-knowledge proof is provided to the challenge issuer to access services of one or more applications. ## Claims ### Claim at position 1 -20. (canceled) ### Claim 21 A computer-implemented method for providing content comprising: receiving a first request from a user for a first content item on a content delivery network (CDN), wherein the first request includes a first universal resource locator (URL) to the first content item, the first URL comprising at least arguments for a first long expiry period, a first short expiry period, and a temporary user identifier; and providing the user access to the first content item in response to determining validity of the first long expiry period of the first URL and authenticating the user, wherein authenticating the user comprises: extracting the temporary user identifier from the first URL, and comparing the temporary user identifier with user data from a login session associated with the first URL. ### Claim 22 (depends on 21) The method of claim 21, further comprising: providing user credentials associated with at least one application to an application server; receiving an attribute-based challenge from the application server, wherein the attribute-based challenge includes a challenge generated using a verifier derived from the attribute; determining a proof to the challenge using the attribute; and accessing services of the application using a login token received from the application server in response to providing the proof. ### Claim 23 (depends on 21) The method of claim 21, further comprising: receiving user credentials associated with at least one application from a mobile device executing the at least one application; generating an attribute-based challenge, wherein the attribute-based challenge includes a challenge generated using a verifier derived from an attribute of the mobile device; receiving proof from the mobile device in response to the challenge; and enabling access to services of the application in response to validating the proof. ### Claim 24 (depends on 21) The method of claim 21, further comprising: registering to use an application with an application server; receiving data regarding an attribute to be used for a login process; deriving a zero-knowledge verifier using a value of the attribute; and providing the encrypted zero-knowledge verifier to the application server. ### Claim 25 (depends on 21) The method of claim 21, further comprising: selecting an attribute of a mobile device executing at least one application to authenticate the user to access the at least one application; transmitting data regarding the selection of the attribute to the mobile device; receiving a zero-knowledge verifier from the mobile device, wherein the zero-knowledge verifier is based on the attribute of the mobile device; and employing the zero-knowledge verifier in authenticating the user to access the at least one application. ### Claim 26 (depends on 21) The method of claim 21, further comprising: receiving an initial communication associated with a user session; generating a data identifier including a dynamic element; updating the dynamic element to indicate an event associated with user is activity; and implementing criteria to determine whether an associated disparity may be actionable. ### Claim 27 (depends on 26) The method of claim 26, further comprising: monitoring the dynamic element of the data identifier; and receiving a value of a dynamic element that may be different than an expected value. ### Claim 28 (depends on 26) The method of claim 26, further comprising requiring a user action in response to one of the associated disparity and receiving an indication of the event associated with user activity. ### Claim 29 (depends on 21) The method of claim 21, wherein determining validity of the first long expiry period comprises one of: determining validity of the first long expiry period based on the argument for the first long expiry period; and determining validity of the first short expiry period based on the argument for the first long expiry period. ### Claim 30 (depends on 21) The method of claim 21, further comprising, further in response to determining authenticating the user is authentic, refreshing the first URL to provide a refreshed URL, wherein the user is provided access to the first content item using the refreshed URL. ### Claim 31 (depends on 21) The method of claim 21, further comprising: receiving a second request for a second content item on the CDN, wherein the second request includes a second URL to the second content item; determining whether a second short expiry period of the second URL is valid; and in response to determining that the second short expiry period of the second URL is valid, providing the user access to the second content item. ### Claim 32 (depends on 21) The method of claim 21, further comprising: receiving a second request for a second content item on the CDN, wherein the second request includes a second URL to the second content item; determining whether a second short expiry period of the second URL is valid; in response to determining that the second short expiry period of the second URL is invalid, determining whether a second long expiry period of the second URL is valid; and in response to determining that the second long expiry period of the second URL is invalid, prohibiting access to the second content item through the second URL. ### Claim 33 (depends on 21) The method of claim 21, wherein the first content item is one of an image, a progressive video, or video on demand (VOD).