Basic authentication using identity and access manager with API key

Patent metadata

Field	Value
Publication number	US-12475211-B2
Application number	US-202218012084-A
Country	US
Kind code	B2
Filing date	Nov 21, 2022
Priority date	Nov 21, 2022
Publication date	Nov 18, 2025
Grant date	Nov 18, 2025

Abstract

A method, apparatus, and computer-readable recording medium for authenticating a client application using two-factor authentication. The method includes receiving, from the client application, a request to access an application programming interface (API), validating, using a first authentication method, the client application for accessing the API, and based on a result of the validating using the first authentication method, validating the client application for accessing the API using a second authentication method, and providing a response to the client application based on the validating using the first authentication method and the second authentication method.

First claim

What is claimed is:

1 . A method, performed by at least one processor, for authenticating a client application using two-factor authentication, the method comprising:
receiving, from the client application, a request to access an application programming interface (API); validating, using a first authentication method, the client application for accessing the API, wherein the first authentication method comprises a basic authentication method; based on a result of the validating using the first authentication method, validating the client application for accessing the API using a second authentication method, wherein the second authentication method comprises validating using an API Key, and the validating using the API Key comprises determining whether the API Key is expired in response to determining that a valid subscription exists for the API and validating the client application using the first authentication method; based on a result of validating using the first authentication method and the second authentication method, sending a service request to a backend service provider; and providing a response to the client application based on the validating using the first authentication method and the second authentication method.

2 . The method of claim 1 , wherein the basic authentication method comprises determining whether a username and password match an entry in a password database.

3 . The method of claim 1 , wherein the validating using the API Key comprises determining whether the valid subscription exists for the API in response to validating the client application using the first authentication method.

4 . The method of claim 1 , wherein the providing the response to the client application comprises providing a message indicating the client application is not authenticated in response to determining that the client application is not valid based on at least one of the first authentication method and the second authentication method.

5 . The method of claim 1 , wherein the providing the response to the client application comprises providing a service response from a backend service in response to determining that the client application is valid based on the first authentication method and the second authentication method.

6 . The method of claim 1 further comprising, wherein the validating using the first authentication method comprises accessing a first cache, and
wherein the validating using the second authentication method comprises accessing a second cache.

7 . An apparatus for authenticating a client application using two-factor authentication, the apparatus comprising:
a memory storing instructions; and at least one processor configured to execute the instructions to:
receive, from the client application, a request to access an application programming interface (API);
validate, using a first authentication, the client application for accessing the API, wherein the first authentication comprises a basic authentication;
based on a result of the validating using the first authentication, validate the client application for accessing the API using a second authentication, wherein the second authentication comprises validating using an API Key, and the validating using the API Key comprises determining whether the API Key is expired in response to determining that a valid subscription exists for the API and validating the client application using the first authentication;
based on a result of validating using the first authentication and the second authentication, send a service request to a backend service provider; and
provide a response to the client application based on the validating using the first authentication and the second authentication.

8 . The apparatus of claim 7 , wherein the at least one processor is further configured to determine whether a username and password match an entry in a password database.

9 . The apparatus of claim 7 , wherein the at least one processor is further configured to determine whether the valid subscription exists for the API in response to validating the client application using the first authentication.

10 . The apparatus of claim 7 , wherein the at least one processor is further configured to provide a message indicating the client application is not authenticated in response to determining that the client application is not valid based on at least one of the first authentication and the second authentication.

11 . The apparatus of claim 7 , wherein the at least one processor is further configured to provide a service response from a backend service in response to determining that the client application is valid based on the first authentication and the second authentication.

12 . The apparatus of claim 7 further comprising, wherein the at least one processor is further configured to:
access a first cache to validate using the first authentication, and
access a second cache to validate using the second authentication.

13 . A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor, for authenticating a client application using two-factor authentication, the method comprising:
receiving, from the client application, a request to access an application programming interface (API); validating, using a first authentication method, the client application for accessing the API, wherein the first authentication method comprises a basic authentication method; based on a result of the validating using the first authentication method, validating the client application for accessing the API using a second authentication method, wherein the second authentication method comprises validating using an API Key, and the validating using the API Key comprises determining whether the API Key is expired in response to determining that a valid subscription exists for the API and validating the client application using the first authentication method; based on a result of validating using the first authentication method and the second authentication method, sending a service request to a backend service provider; and providing a response to the client application based on the validating using the first authentication method and the second authentication method.

14 . The non-transitory computer-readable recording medium of claim 13 , wherein the basic authentication method comprises determining whether a username and password match an entry in a password database.

15 . The non-transitory computer-readable recording medium of claim 13 , wherein the validating using the API Key comprises determining whether the valid subscription exists for the API in response to validating the client application using the first authentication method.

Assignees

• Rakuten Symphony Inc

Inventors

• Aswani Manoj
• Sharma Hemant
• Kumar Ayus
• Malli Tejaswini

Classifications

• H04L9/08

  Key distribution {or management, e.g. generation, sharing or updating, of cryptographic keys or passwords (network architectures or network communication protocols for supporting key management in a packet data network H04L63/06)} · CPC title

• H04L9/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) · CPC title

• H04L9/0894

  Escrow, recovery or storing of secret information, e.g. secret key escrow or cryptographic key storage · CPC title

• G06F21/45 Primary

  Structures or tools for the administration of authentication · CPC title

• G06F21/6218 Primary

  to a system of files or objects, e.g. local or distributed file system or database · CPC title