# US 2026/0019259 A1 · Establishing sessions via a proxy service

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

- Number: US 2026/0019259 A1
- Document ID: US20260019259A1
- Status: Published application
- Kind: A1
- Application number: 19/333,164
- Filed: 2025-09-18
- Published: 2026-01-15
- Earliest claimed: 2024-01-03
- Assignees: Okta, Inc.
- Applicants: Okta, Inc.
- Inventors: Smitha Prasad; Mario John Villaplana; Sajan Andrew Alexander; Mahesh Keralapura Manjunatha; Swaroop Katika; Evan Moses; Zheng Chen; Phoebe Yu
- Web page: https://patentgrep.com/patent/US20260019259A1

## CPC

- H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials}
- 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)}
- G06F 21/33: using certificates
- G06F 21/45: Structures or tools for the administration of authentication
- H04L 9/088: {Usage controlling of secret information, e.g. techniques for restricting cryptographic keys to pre-authorized uses, different access levels, validity of crypto-period, different key- or password length, or different strong and weak cryptographic algorithms (network architectures or network communication protocols for using time-dependent keys in a packet data network H04L63/068)}
- H04L 9/30: Public key, i.e. encryption algorithm being computationally infeasible to invert or user's encryption keys not requiring secrecy
- H04L 9/3226: {using a predetermined code, e.g. password, passphrase or PIN (network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083)}
- H04L 9/3263: {involving certificates, e.g. public key certificate [PKC] or attribute certificate [AC]; Public key infrastructure [PKI] arrangements (network architectures or network communication protocols for supporting authentication of entities using certificates in a packet data network H04L63/0823)}
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- 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

A method for managing sessions with an application server via an identity management system is described. The method may include receiving, via an application protocol interface (API) of a cloud service of the identity management system, a first request associated with a first user for user access to an account of the application server. The API may transmit a second request for a secrets service to encrypt a password associated with the first user to a public key of a keypair. The API may receive a message including the encrypted password and forward the encrypted password to an end-client. The identity management system may establish a session on behalf of the first user for the account of the application server based on the end-client having access to a private key of the keypair.

## Claims

### Claim 1

A method for managing sessions with an application server via an identity management system, comprising:
receiving a first request for user access to an account of the application server, wherein the first request is associated with a first user of the account;
transmitting, and in response to the first request, a second request for a secrets service associated with the identity management system to encrypt a password associated with the first user;
receiving, from the secrets service and in response to the second request, a first message comprising the encrypted password, wherein the first message is received from the secrets service;
transmitting, to an end-client associated with the identity management system and in response to the first message, a second message comprising at least the encrypted password; and
establishing, at the end-client on behalf of the first user, a session for the account of the application server based at least in part on the end-client being operable to decrypt the password.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
checking, after receiving the first request, whether a quantity of users accessing the account satisfies a threshold quantity of users indicated by a policy associated with the application server, wherein establishing the session for the account of the application server is based at least in part on the quantity of users not satisfying the threshold quantity of users.

### Claim 3 (depends on 1)

The method of claim 1, wherein the end-client comprises a software client on a device associated with the first user.

### Claim 4 (depends on 3)

The method of claim 3, further comprising:
decrypting, at the software client, the encrypted password, wherein establishing the session is based at least in part on decrypting the encrypted password.

### Claim 5 (depends on 1)

The method of claim 1, wherein the end-client comprises a gateway associated with the identity management system.

### Claim 6 (depends on 5)

The method of claim 5, wherein transmitting the second message comprises:
transmitting the second message to the end-client comprising a software client associated with the first user, wherein the second message further comprises a certificate usable by the software client for establishing a connection between the software client and the end-client;
receiving, at the gateway, the second message comprising the encrypted password and the certificate; and
establishing the connection with the software client based at least in part on the certificate, wherein establishing the session on behalf of the first user is based at least in part on establishing the connection with the software client.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
decrypting, at the gateway, the encrypted password on behalf of the first user, wherein establishing the session on behalf of the first user is based at least in part on decrypting the encrypted password.

### Claim 8 (depends on 6)

The method of claim 6, wherein the application server is associated with a plurality of users having access to the application server, and wherein transmitting the second message further comprises:
determining that the first user is one of the plurality of users having access to the application server.

### Claim 9 (depends on 8)

The method of claim 8, further comprising:
generating the certificate based at least in part on determine that the first user is one of the plurality of users having access to the application server, wherein the second message comprises the certificate based at least in part on generating the certificate.

### Claim 10 (depends on 1)

The method of claim 1, further comprising:
determining, via the end-client, that the first user is one of a first plurality of users having access to the application server at a first time, wherein establishing the session is based at least in part on the first user having access to the application server at the first time.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
determining, at a second time after establishing the session, that the first user is not one of a second plurality of users having access to the application server at the second time; and
terminating the session based at least in part on the first user not having access to the application server at the second time.

### Claim 12

An apparatus for managing sessions with an application server via an identity management system, comprising:
one or more memories storing processor-executable code; and
one or more processors coupled with the one or more memories and individually or collectively operable to execute the code to cause the apparatus to:
receive a first request for user access to an account of the application server, wherein the first request is associated with a first user of the account;
transmit, and in response to the first request, a second request for a secrets service associated with the identity management system to encrypt a password associated with the first user;
receive, from the secrets service and in response to the second request, a first message comprising the encrypted password, wherein the first message is received from the secrets service;
transmit, to an end-client associated with the identity management system and in response to the first message, a second message comprising at least the encrypted password; and
establish, at the end-client on behalf of the first user, a session for the account of the application server based at least in part on the end-client being operable to decrypt the password.

### Claim 13 (depends on 12)

The apparatus of claim 12, wherein the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:
check, after receiving the first request, whether a quantity of users accessing the account satisfies a threshold quantity of users indicated by a policy associated with the application server, wherein establishing the session for the account of the application server is based at least in part on the quantity of users not satisfying the threshold quantity of users.

### Claim 14 (depends on 12)

The apparatus of claim 12, wherein the end-client comprises a software client on a device associated with the first user.

### Claim 15 (depends on 14)

The apparatus of claim 14, wherein the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:
decrypt, at the software client, the encrypt password, wherein establishing the session is based at least in part on decrypting the encrypted password.

### Claim 16 (depends on 12)

The apparatus of claim 12, wherein the end-client comprises a gateway associated with the identity management system.

### Claim 17 (depends on 16)

The apparatus of claim 16, wherein, to transmit the second message, the one or more processors are individually or collectively operable to execute the code to cause the apparatus to:
transmit the second message to the end-client comprising a software client associated with the first user, wherein the second message further comprises a certificate usable by the software client for establishing a connection between the software client and the end-client;
receive, at the gateway, the second message comprising the encrypted password and the certificate; and
establish the connection with the software client based at least in part on the certificate, wherein establishing the session on behalf of the first user is based at least in part on establishing the connection with the software client.

### Claim 18 (depends on 17)

The apparatus of claim 17, wherein the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:
decrypt, at the gateway, the encrypt password on behalf of the first user, wherein establishing the session on behalf of the first user is based at least in part on decrypting the encrypted password.

### Claim 19 (depends on 17)

The apparatus of claim 17, wherein the application server is associated with a plurality of users having access to the application server, and wherein, to transmit the second message, the one or more processors are individually or collectively further operable to execute the code to cause the apparatus to:
determine that the first user is one of the plurality of users having access to the application server.

### Claim 20

A non-transitory computer-readable medium storing code for managing sessions with an application server via an identity management system, the code comprising instructions executable by one or more processors to:
receive a first request for user access to an account of the application server, wherein the first request is associated with a first user of the account;
transmit, and in response to the first request, a second request for a secrets service associated with the identity management system to encrypt a password associated with the first user;
receive, from the secrets service and in response to the second request, a first message comprising the encrypted password, wherein the first message is received from the secrets service;
transmit, to an end-client associated with the identity management system and in response to the first message, a second message comprising at least the encrypted password; and
establish, at the end-client on behalf of the first user, a session for the account of the application server based at least in part on the end-client being operable to decrypt the password.
