# US 2026/0089010 A1 · Browser-based authentication scheme

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2026/0089010 A1
- Document ID: US20260089010A1
- Status: Published application
- Kind: A1
- Application number: 19/400,876
- Filed: 2025-11-25
- Published: 2026-03-26
- Earliest claimed: 2023-05-19
- Assignees: Shore Labs Zbigniew Zemla
- Applicants: Shore Labs Zbigniew Zemla
- Inventors: Zbigniew Józef ZEMLA
- Web page: https://patentgrep.com/patent/US20260089010A1

## CPC

- H04L 9/3247: {involving digital signatures}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- 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/3218: {using proof of knowledge, e.g. Fiat-Shamir, GQ, Schnorr, ornon-interactive zero-knowledge proofs}
- H04L 9/3271: {using challenge-response}
- H04L 61/4511: using domain name system [DNS]
- H04L 63/123: {received data contents, e.g. message integrity}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Disclosed herein is a method performed by a client application of an authentication provider application. The method includes deriving a reference to a domain name based on an identity handle of a user, querying a domain name system to obtain one or more identity records associated with the identity handle, obtaining one or more public keys based on the one or more identity records, and deriving an authentication endpoint web address based on the identity handle. The authentication endpoint web address is usable to access the authentication provider application. The method further includes sending data to the authentication provider application using the authentication endpoint web address, wherein the authentication provider application is able to access one or more private keys corresponding to the one or more public keys for generating digital signatures. The method further includes receiving, from the authentication provider application, one or more digital signatures.

## Claims

### Claim 1

A method performed by an authentication provider application accessible to a web browser of a user to prove an identity of a user, the method comprising:
obtaining data to be digitally signed, wherein at least part of the data is received from a client application of the authentication provider application that accesses the authentication provider application through the web browser of the user using a uniform resource locator (URL) that is derivable from an identity handle of the user based at least in part on performing a string manipulation operation on the identity handle, wherein the authentication provider application is executed in the web browser of the user under the URL, wherein the URL is different from a web address that is usable to access the client application through the web browser of the user;
causing a digital signature to be generated based on the data and one or more private keys of one or more asymmetric cryptography key pairs; and
sending the digital signature to the client application, wherein the client application is to obtain one or more public keys of the one or more asymmetric cryptography key pairs based on data stored in one or more publicly accessible resource records of a domain name that is derivable from the identity handle of the user and verify the digital signature using the one or more public keys of the one or more asymmetric cryptography key pairs.

### Claim 2 (depends on 1)

The method of claim 1, wherein the URL is pointed at a web server that serves the authentication provider application to the web browser of the user.

### Claim 3 (depends on 1)

The method of claim 1, wherein the authentication provider application is accessible under the URL without a need for the web browser of the user to contact a web server.

### Claim 4 (depends on 1)

The method of claim 1, wherein at least one of the one or more private keys is stored in a client-side storage of the web browser.

### Claim 5 (depends on 1)

The method of claim 1, wherein at least one of the one or more private keys is stored by an external service and the digital signature is provided by the external service to the authentication provider application.

### Claim 6 (depends on 1)

The method of claim 1, wherein the at least part of the data that is received from the client application includes a challenge generated by the client application, wherein the client application is to verify the digital signature using the challenge and authenticate the user if the digital signature is successfully verified.

### Claim 7

A non-transitory machine-readable storage medium storing instructions that, when executed by a computing system implementing an authentication provider application accessible to a web browser of a user, causes the authentication provider application to perform operations comprising:
obtaining data to be digitally signed, wherein at least part of the data is received from a client application of the authentication provider application that accesses the authentication provider application through the web browser of the user using a uniform resource locator (URL) that is derivable from an identity handle of the user based at least in part on performing a string manipulation operation on the identity handle, wherein the authentication provider application is executed in the web browser of the user under the URL, wherein the URL is different from a web address that is usable to access the client application through the web browser of the user;
causing a digital signature to be generated based on the data and one or more private keys of one or more asymmetric cryptography key pairs; and
sending the digital signature to the client application, wherein the client application is to obtain one or more public keys of the one or more asymmetric cryptography key pairs based on data stored in one or more publicly accessible resource records of a domain name that is derivable from an identity handle of the user and verify the digital signature using the one or more public keys of the one or more asymmetric cryptography key pairs.

### Claim 8 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein the URL is pointed at a web server that serves the authentication provider application to the web browser of the user.

### Claim 9 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein the authentication provider application is accessible under the URL without a need for the web browser of the user to contact a web server.

### Claim 10 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein at least one of the one or more private keys is stored in a client-side storage of the web browser.

### Claim 11 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein at least one of the one or more private keys is stored by an external service and the digital signature is provided by the external service to the authentication provider application.

### Claim 12 (depends on 7)

The non-transitory machine-readable storage medium of claim 7, wherein the at least part of the data that is received from the client application includes a challenge generated by the client application, wherein the client application is to verify the digital signature using the challenge and authenticate the user if the digital signature is successfully verified.

### Claim 13

A method performed by an application to encrypt a data item, the method comprising:
obtaining a data encryption key;
encrypting the data item using the data encryption key to generate an encrypted data item;
storing the encrypted data item in a storage location;
obtaining one or more identity handles of one or more users that should be given an ability to access a decrypted form of the data item;
deriving one or more references to one or more domain names based on the one or more identity handles;
querying a domain name system for one or more resource records of the one or more domain names to obtain one or more identity records associated with the one or more identity handles;
obtaining one or more identity public keys associated with the one or more identity handles based on data stored in the one or more identity records; and
for each identity public key included in the one or more identity public keys, performing the following:
a) obtaining a key encrypting key using the identity public key, wherein the identity public key is associated with an identity handle of a user, wherein an authentication endpoint web address derived from the identity handle of the user is usable to access an authentication provider application that has access to an identity private key that cryptographically matches the identity public key for purposes of performing cryptographic algorithms,
b) encrypting the data encryption key using the key encrypting key to generate a wrapped data encryption key, and
c) storing an access key in the storage location, wherein the access key references the data item and includes the wrapped data encryption key.

### Claim 14 (depends on 13)

The method of claim 13, wherein obtaining the key encrypting key using the identity public key comprises:
generating an elliptic-curve (EC) key pair that includes an EC private key and an EC public key; and
generating the key encrypting key using a key agreement algorithm with the EC private key and the identity public key, wherein the EC public key is stored as part of the access key in the storage location.

### Claim 15 (depends on 13)

The method of claim 13, wherein the key encrypting key is the same as the identity public key and an asymmetric encryption algorithm is used to encrypt the data encryption key.

### Claim 16 (depends on 13)

The method of claim 13, wherein obtaining the key encrypting key using the identity public key comprises:
sending the identity public key to an authentication provider application accessible to a web browser of a user that is granting access to the data item; and
receiving the key encrypting key from the authentication provider application, wherein the authentication provider application is to use a key agreement algorithm with the identity public key and a private key accessible to the authentication provider application to generate the key encrypting key.

### Claim 17

A method performed by client application to query a data item:
querying a storage location for the data item;
obtaining, as a result of the querying, an encrypted data item and one or more access keys that reference the data item;
sending data extracted from the one or more access keys to an authentication provider application accessible to a web browser of a user that should have an ability to access a decrypted form of the data item;
receiving a key encrypting key from the authentication provider application, wherein the authentication provider application uses the data to obtain the key encrypting key;
decrypting a wrapped data encryption key extracted from one of the one or more access keys using the key encrypting key to obtain a data encryption key; and
decrypting the encrypted data item using the data encryption key to obtain the decrypted form of the data item.
