# US 2023/0412383 A1 · Systems and methods for inter-service authentication

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

- Number: US 2023/0412383 A1
- Document ID: US20230412383A1
- Status: Published application
- Kind: A1
- Application number: 18/458,555
- Filed: 2023-08-30
- Published: 2023-12-21
- Earliest claimed: 2018-01-09
- Assignees: JPMorgan Chase Bank, N.A.
- Applicants: Jpmorgan Chase Bank, N.A.
- Inventors: Deepak Sarda; Ramji Venkateswaran
- Web page: https://patentgrep.com/patent/US20230412383A1

## CPC

- H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- 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/0825: {using asymmetric-key encryption or public key infrastructure [PKI], e.g. key signature or public key certificates}
- H04L 9/083: {involving central third party, e.g. key distribution center [KDC] or trusted third party [TTP]}
- H04L 9/0894: {Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage}
- 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/3247: {involving digital signatures}
- 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/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/0853: {using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234)}
- H04L 63/0876: {based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems and methods for inter-service authentication are disclosed. In one embodiment, a system may include a plurality of services and a cloud platform. The first service may generate a token comprising a first service identifier for communicating with a second service, and may request, from the cloud platform, a private key for the first service. The cloud platform may provide the private key to the first service. The first service may sign the token with the private key and may communicate a request to the second service with the signed token. The second service may retrieve the first service identifier and may request, from the cloud platform, a public key for the first service identifier. The cloud platform may provide the public key to the second service. The second service may validate the token using the public key, and may grant the request in response to the validation.

## Claims

### Claim at position 1

1-20. (canceled)

### Claim 21

A method for inter-service authentication comprising:
in a cloud platform information processing apparatus comprising at least one computer processor and hosting a first service and a second service:
communicating, by the first service, a first request for a public key associated with the second service from a cloud platform, wherein the first request further comprises a first service identifier for the first service;
receiving, by the first service, the public key associated with the second service from the cloud platform;
encrypting, by the first service, a service request to the second service with the public key associated with the second service;
communicating, by the first service, the encrypted service request to the second service;
communicating, by the second service, a second request for a private key associated with the second service from the cloud platform, wherein the second request further comprises a second service identifier for the second service;
validating, by the cloud platform, the second service using the first service identifier and the second service identifier;
providing, by the cloud platform, the private key for the second service to the second service; and
decrypting, by the second service, the encrypted service request using the private key associated with the second service.

### Claim 22 (depends on 21)

The method of claim 21, wherein the cloud platform generates the private key and the public key.

### Claim 23 (depends on 21)

The method of claim 21, wherein the cloud platform retrieves the private key and the public key from a key vault.

### Claim 24 (depends on 21)

The method of claim 21, wherein the first request and/or the second request are communicated by HTTP.

### Claim 25 (depends on 21)

The method of claim 21, wherein the cloud platform validates the first service before providing the public key for the second service to the first service.

### Claim 26

A system, comprising:
a first service executed in a cloud platform;
a second service executed in the cloud platform; and
a cloud platform computer program executed in the cloud platform;
wherein:
the first service is configured to communicate a first request for a public key associated with the second service to the cloud platform computer program, wherein the first request further comprises a first service identifier for the first service;
the cloud platform computer program is configured to provide the public key associated with the second service to the first service;
the first service is configured to encrypt a service request to the second service with the public key associated with the second service;
the first service is configured to communicate the encrypted service request to the second service;
the second service is configured to communicate a second request for a private key associated with the second service to the cloud platform computer program, wherein the second request further comprises a second service identifier for the second service;
the cloud platform computer program is configured to validate the second service using the first service identifier and the second service identifier;
the cloud platform computer program is configured to provide the private key for the second service to the second service; and
the second service is configured to decrypt the encrypted service request using the private key associated with the second service.

### Claim 27 (depends on 26)

The system of claim 26, wherein the cloud platform computer program is configured to generate the private key and the public key.

### Claim 28 (depends on 26)

The system of claim 26, wherein the cloud platform computer program is configured to retrieve the private key and the public key from a key vault.

### Claim 29 (depends on 26)

The system of claim 26, wherein the first request and/or the second request are communicated by HTTP.

### Claim 30 (depends on 26)

The system of claim 26, wherein the cloud platform computer program is configured to validate the first service before providing the public key for the second service to the first service.
