Authenticating and authorizing application programming interface calls through multiple factors

By adopting a two-factor authorized identity access management system in the cloud computing environment, using client security certificates and IAM tokens or API keys for dual authentication, the problem of insufficient access security between cloud computing services is solved, and high Security and reliable service access.

CN118901222APending Publication Date: 2024-11-05INTERNATIONAL BUSINESS MACHINE CORPORATION
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380029021.3
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-03-23
Filing Date
2023-02-20
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

The access methods between cloud computing services in the prior art are insufficient, the computing cost is high and complex, making it difficult to achieve high-security service access through two-factor authorization.

Method used

Through the service application programming interface protected by the identity access management system, a two-factor authorization method is adopted, and a client security certificate and IAM token or API key are used for dual authentication to ensure the first identity pass key and the second identity pass key. Correctness to initiate service execution.

Benefits of technology

It significantly improves the security of service calls in cloud computing environments, reduces the probability of abuse of services, improves the operational reliability of public, hybrid and private cloud environments, and ensures protection of sensitive data and critical infrastructure.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901222A_ABST
    Figure CN118901222A_ABST
Patent Text Reader

Abstract

A method of authenticating and authorizing a user identifier access service is disclosed. The service is activated by a service application programming interface that requires two-factor authorization to initiate the service executing the requesting user identifier. The method receives a service request and first and second data of first and second authentication methods through a service API, confirms correctness of the first data as a first identity pass key using the first authentication method, and confirms correctness of the second data as a second identity pass key using the second authentication method, and the first identity pass key is input to a second authentication method, the second authentication method being different from the first authentication method. And after the correctness confirmation of the first identity passing key and the second identity passing key is received, executing the service.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention generally relates to an authentication and authorization method, and more particularly to a computer-implemented method for authenticating and authorizing a user identifier to access a service. The present invention further relates to an authentication and authorization system for authenticating and authorizing a user identifier to access a service, and a computer program product for authenticating and authorizing a user identifier to access a service. Background Art

[0002] Privacy and data security have always been a priority for corporate IT (Information Technology) departments. The use of two-factor authorization methods has become quite common in user authentication. Two-factor authentication has not only become a common standard for accessing banking applications, but is also used in many corporate applications. For example, a user who wants to access a specific corporate application must enter a password and a code received separately on a smartphone.

[0003] Due to the widespread use of cloud computing services, access from one cloud service to another can be done either completely insecurely through an application programming interface (API) or through simple authentication mechanisms. More sophisticated and reliable access methods are still rare, such as between one service and another, or by using user identifiers to access cloud services from an identified user through an API.

[0004] There is some public information focusing on the topic of more secure access between computing services. For example, document US2017 / 0161486A1 describes an API authentication method using two API tokens, which includes issuing a general API token to a user device and providing information required for a one-time API token. In addition, document US2009 / 0132807A1 discloses a method and apparatus for providing a secure connection with a server supporting SSL / TSL (Secure Sockets Layer; Transport Layer Security). In one embodiment, a network client establishes a new connection by initiating communication with a server supporting SSL / TSL. The communication includes a non-POST request. After the client negotiates a secure connection with the server in response to the non-POST request, the client submits a POST request to the server supporting SSL / TSL over a secure connection.

[0005] Disadvantages of known solutions may be that they are computationally expensive, very complex to handle, and not user-friendly.

[0006] Therefore, there may be a need to overcome these limitations and provide highly secure API-based access to services, such as cloud computing services. Summary of the invention

[0007] According to one aspect of the present invention, a computer-implemented method for authenticating and authorizing a user identifier to access a service may be provided. The service may be protected by an identity access management system, and the service may be activated through a service application programming interface (API) that requires two-factor authorization to initiate execution of the service for the requesting user identifier.

[0008] The method may include receiving a service request and first data for a first authentication method and second data for a second authentication method through the application programming interface of the service, confirming the correctness of the first data as a first identity pass key using the first authentication method, confirming the correctness of the second data as a second identity pass key using the second authentication method, wherein the first identity pass key is used as input to the second authentication method, and wherein the second authentication method is different from the first authentication method.

[0009] Additionally, the method may include performing the service upon receiving confirmation of the first identity pass key and the second identity pass key.

[0010] According to another aspect of the present invention, there may be provided an authentication and authorization system for authenticating and authorizing a user identifier to access a service. The service may be protected by an identity access management system, and the service may be activated via a service application programming interface that requires two-factor authorization to initiate execution of the service for the requesting user identifier.

[0011] The system may include a processor and a memory communicatively coupled to the processor, wherein the memory stores a program code portion that, when executed, enables the processor to receive a service request and first data for a first authentication method and second data for a second authentication method through the application programming interface of the service.

[0012] The processor is also capable of confirming the correctness of the first data as a first identity pass key using the first authentication method, confirming the correctness of the second data as a second identity pass key using the second authentication method, wherein the first identity pass key is used as input to the second authentication method, wherein the second authentication method is different from the first authentication method, and executing the service after receiving confirmation of the first identity pass key and the second identity pass key.

[0013] The proposed computer-implemented method for authenticating and authorizing a user identifier to access a service may provide various advantages, technical effects, contributions and / or improvements:

[0014] In summary, embodiments of the present invention recognize that service invocation in a cloud computing environment may be significantly enhanced. Current technologies that use IAM (identity and access management) tokens to invoke services, or those that use IAM API keys as the only authentication method to invoke services, can be significantly improved. Embodiments can improve the operational reliability of public, hybrid and / or private cloud computing environments. Although the underlying computing technology may be based on cloud computing principles, unauthorized access to services that process sensitive data or affect critical infrastructure components (such as power grids, gas distribution systems, water supply networks, or power plant controls) can be prevented. Generally available services can only be accessed using two authentication methods that must be different, which requires that both authentication methods be controlled by the IAM system, thereby improving security.

[0015] As a result, successfully implemented two-factor / two-method authorization techniques (e.g. when accessing a bank account or a shopping portal) can now be used in cloud computing with the astonishing effect of reducing the probability of misuse of generally available services to at least 1 / 100.

[0016] In general, the two-factor authentication method can be selected according to the choice of the implementer. However, a preferred embodiment may include implementing the first authentication method using a client certificate (i.e., the certificate for calling the service). As a second authentication method, an IAM token or IAM API key may be successfully used. The options for authentication methods may provide different implementation options.

[0017] Therefore, if the API may require two authentications but only one is successful, the called service in the cloud computing environment will not begin execution (ie, not started or not callable).

[0018] Other embodiments of the inventive concept will be described below, which are also applicable to methods, computer program products and systems.

[0019] According to a preferred embodiment of the method, the first authentication method can be based on a client security certificate. In addition, the second authentication method can be based on a security token or an application programming interface key. Although other authentication method combinations can be used in general, the above combination of the present embodiment can start with the security certificate of the client or client system, achieving relatively less complexity. In addition, for the second authentication method, two alternatives can be considered, which may be beneficial to potential implementers.

[0020] According to another advantageous embodiment of the method, the first authentication method can use the mTLS (mutual transport layer security, TLS for short) standard. This implementation can be implemented by any version or any release of the mTLS standard. mTLS is widely used in the zero-trust security framework to authenticate users, devices and servers in an organization. Therefore, mTLS can also be used as a basic interface protocol for mutual authentication of APIs.

[0021] According to an embodiment of the method, the correctness of the first data and the second data may be confirmed by an Identity Access Management (IAM) system. The first and second authentication methods may be secured by the same or different IAM systems, which may expand the implementation options of the proposed concept.

[0022] According to certain embodiments of the method, the confirmation of the first data and the confirmation of the second data can be performed by the requested service or by a separate service that is in communication with the requested service. These options can provide interesting implementation schemes. The independent service can be a component of the requested service (i.e., a service that is executed after authentication is established), or the independent service can be an independent service that can be used by multiple different requested services.

[0023] According to an optional embodiment of the method, the client certificate may come from an identity access management system (e.g., may be generated by an IAM system). Alternatively, according to another optional embodiment of the method, the client certificate may also be generated by the user and then uploaded. Therefore, the main method may have different implementation schemes.

[0024] According to an enhanced embodiment of the method, the requested service may be integrated into a combined service, such that the security service part may be integrated into the combined service and may include an mTLS endpoint of the first authorization method.

[0025] According to one embodiment of the method, the security service may also include an internal security service for authentication via a token or an application programming interface key. As an alternative, an IAM system may also be used for these two authentication activities.

[0026] According to an optional embodiment of the method, the requested service can be performed in a cloud computing environment. This may be particularly meaningful for users who provide or request a large number of different cloud computing services in a hybrid cloud or multi-cloud environment. In this case, the security and integrity of data and user access may be increased above the security threshold to comply with government regulations.

[0027] In addition, embodiments of the present invention may also take the form of an associated computer program product, accessible from a computer-readable storage medium providing program code, for use with or in connection with any programmable instruction execution device or system. For purposes of this description, a computer-readable storage medium may be any device that may include means for storing, communicating, propagating or transmitting a program, for use with or in connection with a programmable instruction execution system, device or apparatus. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] It should be noted that embodiments of the present invention are described with reference to different subject matters. In particular, some embodiments are described with reference to method-type claims, while other embodiments are described with reference to apparatus-type claims. However, a person skilled in the art will appreciate from the above and below descriptions that, unless otherwise notified, any combination of features relating to different subject matters, in particular the combination of features of method-type claims with features of apparatus-type claims, in addition to any combination of features belonging to one subject matter, are deemed to be disclosed herein.

[0029] The aspects defined above and further aspects of the present invention are apparent from the embodiments described hereinafter and are explained herein with reference to the embodiments but are not limited thereto.

[0030] Preferred embodiments of the present invention will be described by way of example with reference to the following drawings:

[0031] Figure 1 A block diagram of an embodiment of the present invention's computer-implemented method for authenticating and authorizing a user identifier to access a service is shown.

[0032] Figure 2a A block diagram showing access methods for known service APIs.

[0033] Figure 2b A block diagram showing a known method of accessing a service API.

[0034] Figure 3 A communication diagram illustrating the basic mechanisms of the mutual transport layer security (mTLS) protocol is shown.

[0035] Figure 4 A communication diagram showing the main communication flow of components illustrating the proposed concepts.

[0036] Figure 5 A block diagram of an embodiment of a system for authenticating and authorizing a user identifier to access a service is shown.

[0037] Figure 6 Shows the Figure 5 Embodiments of a computing system.

[0038] Figure 7 A cloud computing environment is shown in which at least a portion of the inventive concepts may be deployed.

[0039] Figure 8 The components of a cloud computing environment are shown. DETAILED DESCRIPTION

[0040] In the context of this description, the following conventions, terms and / or expressions may be used:

[0041] The term 'authentication and authorization' denotes a two-step process in which, first, the calling or requesting entity must establish a confirmed authentication (i.e., verification), and second, the authenticated entity can obtain authorization to access certain resources (i.e., the requested service). For example, a cloud computing environment can be used, in which the first step includes confirming the correct authentication of the requester. The first authentication confirmation step can be performed by an IAM API key or IAM token used in a TLS connection. In some embodiments, a policy enforcement point (PEP) can be enabled to intercept a user's access request and call a policy decision point (PDP), which can evaluate the access request and execute a decision based on the authorization policy. In this environment, a policy administration point (PAP) collaborates with the PDP to manage access authorization policies.

[0042] It may be added that the authentication method used here should be structured so that the implementation does not require user intervention (i.e., the implementation of the authentication method does not require user input). In general, the authentication factor can take the form of a username and password, an IAM token, an IAM API key, a client certificate, or an algorithm that can determine a TOTP (Time-based One-time Password) value from a stored secret.

[0043] The term "user identifier" may refer to a code used to uniquely identify (e.g., a UID) a user operating a computing device application who makes a request (i.e., a service call) to an API of a service or an API of a related service. The use of a user identifier helps to explicitly manage access rights to a service (e.g., to handle access to sensitive data).

[0044] The term "accessing a service" may refer to performing a service request from one service to another service using an API.

[0045] The term "Identity Access Management System" (IAM System), also known as Identity and Access Management (IdAM System), can be based on a policy and technical framework to ensure that the right users (in an enterprise) have appropriate access to technical resources. Identity and Access Management Systems fall under the overall scope of Information Technology (IT) security and data management. Identity and Access Management Systems not only identify, authenticate and control access rights of individuals who will use IT resources, but also identify, authenticate and control the hardware and applications that employees need to access.

[0046] The term "application programming interface" (API) refers to a connection between computers or between computer programs (i.e., services). An API can be a software interface that provides services to other software. The file or standard that describes how to establish or use such a connection or interface is called an API specification.

[0047] The term "two-factor authentication" refers to the use of two different security methods before access to a service is allowed (i.e., before a service is requested or a user submitting a service request is authorized to access or perform the service).

[0048] The term "service request" means the invocation of one service from another service.

[0049] The terms "first data" and "second data" refer to data used in the first authentication method and the second authentication method, respectively.

[0050] The term "identity passkey" may be considered equivalent to the first data in the first authentication method and the second data in the second authentication method.

[0051] The term "client security credentials" refers to a code generated by IAM or a calling service that confirms the identity of a client.

[0052] The term "security token" refers to a code required to access a service, where the security token can be validated by the IAM system before the service can be executed.

[0053] The term "Application Programming Interface Key" (API Key) refers to a code without which an API cannot be accessed (i.e., the API is protected by an API Key). Therefore, without providing the correct API Key and other parameters required by the API, the service initiated by accessing the API will not be able to execute.

[0054] The term "mTLS standard" refers to what is known as Mutual Transport Layer Security (mTLS or simply TLS). As a protocol, mTLS is a cryptographic protocol designed to provide communication security over computer networks. Secure Sockets Layer (SSL) is the widely used successor protocol to mTLS.

[0055] The term "cloud computing" and the more specific term "cloud service environment" can be interpreted in the current context as a model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (such as networks, servers, storage, applications, and services) that can be quickly provisioned and released with minimal management effort or service provider interaction. The cloud service environment model promotes availability and consists of at least five basic characteristics, three service models, and four deployment models.

[0056] It should be understood that although the present disclosure includes a detailed description of cloud computing, implementation of the teachings described herein is not limited to a cloud computing environment. Rather, embodiments of the present invention can be implemented in conjunction with any other type of computing environment now known or later developed. Cloud computing is a service delivery model for enabling convenient, on-demand network access to a shared pool of configurable computing resources (e.g., networks, network bandwidth, servers, processing, memory, storage, applications, virtual machines, and services) that can be quickly provisioned and released with minimal management effort or interaction with a service provider. Such a cloud model may include at least five features, at least three service models, and at least four deployment models.

[0057] The basic characteristics of cloud computing include:

[0058] On-demand self-service : Consumers can unilaterally and automatically provision computing resources, such as server time and network storage, when needed, without having to manually interact with each service provider.

[0059] Extensive network access : Provide resources and functionality over a network and access them through standard mechanisms, thereby facilitating the use of heterogeneous thin or thick client platforms (such as mobile phones, laptops, and PDAs).

[0060] Resource Pool : The computing resources of the provider are pooled through a multi-tenant model to provide services to multiple consumers, and different physical and virtual resources can be dynamically allocated and reallocated according to the needs of consumers. Customers generally have no control or knowledge of the exact location of the provided resources, but can specify the location at a higher level of abstraction (such as country, state, or data center), so it has location independence. Examples of resources include storage, processing, memory, network bandwidth, and virtual machines.

[0061] Fast elasticity : Computing resources can be quickly and elastically deployed, and in some cases automatically deployed, to quickly expand, and quickly released, to quickly reduce. For consumers, the computing resources available for deployment are often unlimited and can be purchased at any time and in any quantity.

[0062] Metering Services :Cloud systems automatically control and optimize resource usage by leveraging metering capabilities at an abstraction level appropriate to the type of service (such as storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency to providers and consumers of the services used.

[0063] Service models for cloud computing include:

[0064] Software as a Service(SaaS): The service functionality provided to consumers is the use of the provider's applications running on the cloud infrastructure. These applications are accessed from a variety of client devices (such as web-based email) through a thin client interface (such as a web browser). The consumer does not manage or control the underlying cloud infrastructure, including the network, servers, operating systems, storage, or even the functionality of individual applications, with the possible exception of limited user-specific application configuration settings.

[0065] Platform as a Service (PaaS): The service function provided to consumers is to deploy applications created or acquired by consumers on cloud infrastructure. These applications are created using programming languages ​​and tools supported by the provider. Consumers do not manage or control the underlying cloud infrastructure (including networks, servers, operating systems, or storage), but can control the deployed applications and possibly the configuration of the application hosting environment.

[0066] Infrastructure as a Service (IaaS): The service capabilities provided to consumers include the provision of processing, storage, network and other basic computing resources, on which consumers can deploy and run arbitrary software, including operating systems and applications. Consumers do not manage or control the underlying cloud infrastructure, but have control over the operating system, storage, deployed applications, and may have limited control over selected network components (such as host firewalls).

[0067] Cloud computing deployment models include:

[0068] Private Cloud : Cloud infrastructure is operated solely by the organization. It can be managed by the organization or a third party and can exist on or off premises.

[0069] Community Cloud : Cloud infrastructure is shared by multiple organizations to support a specific community with common concerns such as mission, security requirements, policies, and compliance considerations. It may be managed by the organization or a third party and may exist on-premises or off-premises.

[0070] Public Cloud : Cloud infrastructure is open to the public or large industry groups and is owned by the organizations that sell cloud services.

[0071] Hybrid Cloud : A cloud infrastructure consists of two or more clouds (private, community, or public) that remain distinct entities but are bound together by standardized or proprietary technologies to enable data and application portability (e.g., cloud bursting for load balancing between clouds).

[0072] The cloud computing environment is service-oriented and focuses on statelessness, low coupling, modularity, and semantic interoperability. The core of cloud computing is the infrastructure including the network of interconnected nodes.

[0073] It can be noted that cloud software fully utilizes the advantages of the cloud model, is service-oriented, and focuses on statelessness (exceptions), low coupling, modularity, and semantic interoperability.

[0074] Each figure will be described in detail below. All descriptions in the figures are schematic diagrams. Figure 1 A block diagram of an embodiment of a computer-implemented method of authenticating and authorizing a user identifier to access a service is shown. Subsequent figures describe and depict various aspects of other embodiments of an authentication and authorization system for authenticating and authorizing a user identifier to access a service.

[0075] Figure 1 A block diagram of a preferred embodiment of a computer-implemented method 100 for authenticating and authorizing a user identifier to access a service is shown. The service is protected by an identity access management system, and the service is activated through a service application programming interface (API) that requires two-factor authorization to initiate execution of the service for the requested user identifier. For two-factor authorization, the preferred solution is based on client certificates and IAM tokens. Method 100 includes receiving a service request through the service's application programming interface (step 102). The received request includes first data for a first authentication method, which can be the client security certificate described above. The received request also includes second data for a second identity authentication method, which in some embodiments can be a security token.

[0076] Method 100 confirms the correctness of the first data using a first authentication method (step 104). In some embodiments, method 100 uses an IAM system to confirm whether the first data correctly matches a first identity pass key of the first authentication method. Method step 106 confirms the correctness of the second data, which can also be confirmed using an IAM system using a second identity pass key that is different from the first identity pass key. For a two-factor authentication method, the confirmed correct first identity pass key is used as input to enable use of the second identity pass key for the second authentication method. In addition, the second authentication method is different from the first authentication method.

[0077] Furthermore, after receiving and validating the first identity passkey and receiving and validating the second identity passkey, method step 108 activates execution of the service and optionally provides the result of the service to the requesting / calling service via the service API.

[0078] Figure 2a and Figure 2bTwo block diagrams 200a, 200b are shown, with known service API access methods as background information. Figure 2a A known method of requester 208 calling services 202, 204, 206 is shown, where each service has an API. Requester 208 uses an API key to access IAM system 210 to obtain an IAM access token, and can enter a service request using the API by confirming the IAM API key.

[0079] Figure 2b A known implementation is shown in which a requester 208 accesses services 202, 204, 206, each of which has an API, through an IAM API key. The IAM API key can be verified by an IAM system 210.

[0080] Figure 3 A communication diagram 300 is shown illustrating the basic mechanisms of the mTLS security protocol between a client 302 and a server 304, which may also be used as part of the two-factor authentication method proposed herein. The client 302 sends a synchronization signal 306 to the server 304. The server 304 sends a synchronization confirmation signal 308 to the client 302. A client "hello" signal 310 and a server "hello" signal 312 are exchanged, wherein the server "hello" signal 312 includes the completed certificate server hello. The client 302 responds with a client_key exchange signal 314 and receives a change_cypher_spec_finished signal 316 from the server.

[0081] According to the protocol, the server must identify itself by presenting an SSL (Secure Sockets Layer) certificate; the server needs to possess the appropriate private key belonging to the SSL certificate. Optionally, the client identifies itself by presenting an SSL certificate, and the client needs to possess the appropriate private key belonging to the SSL certificate.

[0082] Figure 4 The communication diagram 400 shown illustrates the main communication flow of the components of the proposed concept. Figure 4 The components in FIG. 3 include a client 302, a server service 304 with a TLS endpoint, and a server service 306 with an API implementation. Server services 304 and 306 can be separate services, or the service TLS endpoint 304 can be integrated into server service 306. The common dashed line around server service 304 and server service 306 represents the potential integration of the two services.

[0083] The protocol first sends an API request 312 with an IAM token via mTLS. The server service 304 with a TLS endpoint verifies the client certificate 314 using the IAM server 310, establishing authentication / authorization identity 1. Subsequently, the server service 304 with a TLS endpoint sends an API request 316 with the IAM token and authentication identity 1 from the client certificate to the server service 306, including the service request from the client 302. The server service 306 verifies the IAM token 318 and establishes authentication / authorization identity 2.

[0084] In addition, service 306 performs authentication check 1, 320 against identities 1 and 2 to confirm the authorization of identities 1 and 2 for the first operation (i.e., confirming the authorization of identity 1 or 2 for the "GET" command operation), and performs another authentication check 2, 322 against the remaining identities of identities 1 and 2 for the second operation (i.e., authorizing the "CONNECT" command to connect to the API to access the requested service). These two authentication checks represent PEP activities (discussed previously). After confirming the authorization of the operations for both authentications, service 306 performs API operation 324 to perform the requested service function. The server service 304 with TLS endpoint receives the result 326 and sends the result 328 to the calling or requesting client 302 (or the service of the requesting client 302).

[0085] IAM-enabled services require two permissions to start the requested service. Confirmation of the first identity verifies and confirms that identity 1 has an associated policy that allows the first operation (i.e., (i) operation "GET"). Confirmation of the second identity verifies and confirms that identity 2 has an associated policy that allows the second operation (i.e., "CONNECT"). Identity 1 and identity 2 serve as the two-factor authentication / authorization components of an embodiment of the present invention to authorize requests for services provided by the API.

[0086] Figure 5 A block diagram of an embodiment of a method 500 for authenticating and authorizing a user identifier to access a service is shown. Here, the service is also protected by an identity access management system, and the service can be activated by a service application programming interface that requires a two-factor authorization to begin executing the service requesting the user identifier. The system 500 includes a processor 502 and a memory 504 communicatively coupled to the processor 502, wherein the memory stores a program code portion that, when executed, enables the processor 502 to receive a service request via a receiving unit 506, the request including first data for a first authentication method and second data for a second authentication method, so as to access and receive the requested service from the service's application programming interface.

[0087] The processor 502 can also confirm the correctness of the first data as the first identity pass key using the first authentication method through the first confirmation unit 508, and confirm the correctness of the second data as the second identity pass key using the second authentication method through the second confirmation unit 510. Therefore, the first identity pass key and the second data are used as inputs of the second authentication method, and the second authentication method is different from the first authentication method.

[0088] Furthermore, after receiving the second identity pass key and the first identity pass key determined by the determination unit “All keys received?” 512 , the processor 502 is further able to execute a service, in particular with the support of the service execution module 514 .

[0089] It should also be mentioned that all functional units, modules and functional blocks, in particular the processor 502, the memory 504, the receiver unit 506, the first confirmation unit 508, the second confirmation unit 510, the determination unit 512 and the service execution module 514, can be communicatively coupled to each other in a selected one-to-one manner for signal or message exchange. Alternatively, these functional units, modules and functional blocks can be connected to the system internal bus system 516 for selected signal or information exchange.

[0090] Embodiments of the present invention may be implemented with virtually any type of computer, whether or not the platform is suitable for storing and / or executing program code. Figure 6 A computing system 600 suitable for executing program code associated with the methods of the present invention is shown.

[0091] The computing system 600 is only one example of a suitable computer system and does not imply any limitation on the scope of use or functionality of the embodiments of the present invention described herein, regardless of whether the computer system 600 is capable of implementing and / or performing any of the functions described herein. In the computer system 600, there are some components that can operate with many other general or special computing system environments or configurations. Examples of well-known computing systems, environments, and / or configurations that may be applicable to the computer system / server 600 include, but are not limited to, personal computer systems, server computer systems, thin clients, thick clients, handheld or laptop devices, multiprocessor systems, microprocessor-based systems, set-top boxes, programmable consumer electronics, network PCs, microcomputer systems, large computer systems, and distributed cloud computing environments including any of the above systems or devices, etc. The computer system / server 600 can be described in the general case where computer system executable instructions (such as program modules) are executed by the computer system 600. In general, program modules may include routines, programs, objects, components, logic, data structures, etc. that perform specific tasks or implement specific abstract data types. The computer system / server 600 can be used in a distributed cloud computing environment in which tasks are performed by remote processing devices connected through a communication network. In a distributed cloud computing environment, program modules may be located in both local and remote computer system storage media, including memory storage devices.

[0092] As shown, computer system / server 600 is displayed in the form of a general computing device. The components of computer system / server 600 may include, but are not limited to, one or more processors or processing units 602, system memory 604, and a bus 606 connecting various system components including system memory 604 to processor 602. Bus 606 represents one or more of a variety of types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, and a processor or local bus using any of a variety of bus architectures. For example, such architectures include an industrial standard architecture (ISA) bus, a microchannel architecture (MCA) bus, an enhanced ISA (EISA) bus, a video electronics standard association (VESA) local bus, and a peripheral component interconnect (PCI) bus, but are not limited thereto. Computer system / server 600 typically includes various computer system readable media. These media can be any available media accessible to computer system / server 600, including volatile and non-volatile media, and removable and non-removable media.

[0093] The system memory 604 may include computer system readable media in the form of volatile memory, such as random access memory (RAM) 608 and / or cache memory 610. The computer system / server 600 may further include other removable / non-removable, volatile / non-volatile computer system storage media. For example, the storage system 612 may be used to read and write non-removable, non-volatile magnetic media (not shown, commonly referred to as a "hard drive"). Although not shown, a disk drive for reading data from and writing data to a removable, non-volatile disk (e.g., a "floppy disk"), and an optical drive for reading data from or writing data to a removable, non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In this case, each drive may be connected to the bus 606 via one or more data media interfaces. As will be further described below, the memory 604 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of an embodiment of the present invention.

[0094] The program / utility has a set (at least one) of program modules 616 that can be stored in the memory 604, for example, but not limited to, an operating system, one or more application programs, other program modules, and program data. Each operating system, one or more application programs, other program modules, and program data, or some combination thereof, can include an implementation of a network environment. The program modules 616 generally perform the functions and / or methods of the embodiments of the present invention described herein.

[0095] The computer system / server 600 may also communicate with one or more external devices 618, such as a keyboard, a pointing device, a display 620, etc.; one or more devices that enable a user to interact with the computer system / server 600; and / or any device that enables the computer system / server 600 to communicate with one or more other computing devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface 614. In addition, the computer system / server 600 may also communicate with one or more networks, such as a local area network (LAN), a general wide area network (WAN), and / or a public network (e.g., the Internet) via a network adapter 622. As shown, the network adapter 622 may communicate with other components of the computer system / server 600 via a bus 606. It should be understood that, although not shown, other hardware and / or software components may also be used in conjunction with the computer system / server 600. For example, these include, but are not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data archiving storage systems.

[0096] Additionally, the authentication and authorization system 500 method for authenticating and authorizing a user identifier to access a service may be attached to the bus system 606 .

[0097] Figure 7 A cloud computing environment 700 is shown in which at least a portion of the inventive concept may be deployed. The figure shows a set of functional abstraction layers provided by the cloud computing environment. It should be understood in advance that Figure 7 The components, layers, and functions shown in are for illustration only, and embodiments of the present invention are not limited thereto. As shown, the following layers and corresponding functions are provided: Hardware and software layer 702 includes hardware and software components. Examples of hardware components include: host 704; server 706; server 708 based on RISC (reduced instruction set computer) architecture; blade server 710; storage device 712; network 714 and network component 714. In some embodiments, software components include network application server software 716 and / or database software 718.

[0098] Virtualization layer 720 provides an abstraction layer from which the following examples of virtual entities may be provided: virtual servers 722 , virtual storage 724 , virtual networks 726 (including virtual private networks), virtual applications and operating systems 728 , and virtual clients 730 .

[0099] In one example, the management layer 732 may provide the following functionality. Resource provisioning 734 provides dynamic procurement of computing resources and other resources that are used to perform tasks in a cloud computing environment. Metering and pricing 736 provides cost tracking when resources are used in a cloud computing environment and bills or invoices the consumption of these resources. In one example, these resources may include application software licenses. Security provides authentication for cloud consumers and tasks and provides protection for data and other resources. User portal 738 provides access to the cloud computing environment for consumers and system administrators. Service level management 740 provides cloud computing resource allocation and management to meet the required service levels. Service level agreement (SLA) planning and fulfillment 742 provides pre-scheduling and procurement of cloud computing resources, anticipating future demand based on the SLA.

[0100] The workload layer 744 provides examples of functions that can utilize the cloud computing environment. Examples of workloads and functions that can be provided by this layer include: mapping and navigation 746; software development and lifecycle management 748; virtual classroom education delivery 750; data analysis processing 752; transaction processing 754; and other endpoint services or systems 756, such as the inventive concept of two-factor authentication and authorization for API service delivery described herein (see also Figure 5 , 500).

[0101] Figure 8Components 800 of a cloud computing environment 802 are shown. As shown, the cloud computing environment 802 includes one or more cloud computing nodes 804, with which local computing devices used by cloud consumers, such as personal digital assistants (PDAs) or cellular phones 806, desktop computers 808, laptop computers 810, and / or automotive computer systems 812, can communicate. The nodes 804 can communicate with each other. They can be physically or virtually grouped in one or more networks (private clouds, community clouds, public clouds, or hybrid clouds as described above) or a combination thereof (not shown). In this way, the cloud computing environment 802 can provide infrastructure, platforms, and / or software as a service to cloud consumers, who do not need to maintain resources on local computing devices. It will be appreciated that Figure 8 The types of computing devices 804 shown are for illustration only, and computing nodes 10 and cloud computing environment 802 may communicate with any type of computerized device via any type of network and / or network addressable connection (eg, using a Web browser).

[0102] The description of various embodiments of the present invention is presented for the purpose of illustration, but is not intended to be exhaustive or limited to the disclosed embodiments. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the described embodiments. The terms used herein are intended to best explain the principles of the embodiments of the present invention, their practical applications, or technical improvements over the prior art on the market, or to enable those of ordinary skill in the art to understand the embodiments disclosed herein.

[0103] The present invention may be embodied as a system, a method and / or a computer program product. The computer program product may include a computer-readable storage medium (or medium) having computer-readable program instructions thereon for causing a processor to perform various aspects of the present invention.

[0104] The medium may be a propagation medium of an electronic, magnetic, optical, electromagnetic, infrared or semiconductor system. Examples of computer readable media may include semiconductor or solid-state memory, magnetic tape, removable computer floppy disk, random access memory (RAM), read-only memory (ROM), hard disk and optical disk. Current examples of optical disks include compact disk - read only memory (CD-ROM), compact disk - read / write (CD R / W), DVD and Blu-ray disk.

[0105] A computer-readable storage medium may be a tangible device that can retain and store instructions for use by an instruction execution device. For example, a computer-readable storage medium may be, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the above devices. A non-exhaustive list of more specific examples of computer-readable storage media includes the following: portable computer floppy disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), static random access memory (SRAM), portable compact disk read-only memory (CD-ROM), digital versatile disk (DVD), memory stick, floppy disk, mechanical encoding device (such as a punch card or a raised structure with instructions recorded in a groove), and any suitable combination of the above devices. The computer-readable storage medium used herein should not be understood as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagating through a waveguide or other transmission medium (such as a light pulse through a fiber optic cable), or an electrical signal transmitted through a wire.

[0106] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to a respective computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network may include copper transmission cables, optical transmission fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network and forwards the computer-readable program instructions to a computer-readable storage medium in the corresponding computing / processing device for storage.

[0107] The computer-readable program instructions for performing the operation of the present invention can be assembly instructions, instruction set architecture (ISA) instructions, machine instructions, machine-related instructions, microcode, firmware instructions, state setting data, or source code or object code written in any combination of one or more programming languages ​​(including object-oriented programming languages, such as Smalltalk, C++ or similar languages) and traditional program programming languages ​​(such as C programming language or similar programming languages). The computer-readable program instructions can be executed completely on the user's computer, can also be executed on the user's computer as a separate software package, can also be executed partly on the user's computer, can be executed partly on a remote computer, or can be executed completely on a remote computer or server. In the latter case, the remote computer can be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), and can also be connected to an external computer (for example, through the Internet of an Internet service provider). In certain embodiments, the electronic circuit including, for example, a programmable logic circuit, a field programmable gate array (FPGA) or a programmable logic array (PLA) can execute the computer-readable program instructions by utilizing the state information of the computer-readable program instructions, to personalize the electronic circuit, thereby executing various aspects of the present invention.

[0108] Various aspects of the present invention are described herein with reference to flowchart illustrations and / or block diagrams of methods, devices (systems) and computer program products according to embodiments of the present invention. It is understood that each block in the flowchart illustrations and / or block diagrams and combinations of blocks in the flowchart illustrations and / or block diagrams can be implemented by computer-readable program instructions.

[0109] These computer-readable program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce means for implementing the functions / behaviors specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions may also be stored in a computer-readable storage medium, which may direct a computer, a programmable data processing device, and / or other device to operate in a particular manner, so that the computer-readable storage medium having the instructions stored therein comprises an article of manufacture, which comprises instructions for implementing various aspects of the functions / behaviors specified in the flowchart and / or block diagram block or multiple blocks.

[0110] Computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device, so that a series of operating steps are executed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable apparatus, or other device to implement the functions / behaviors specified in the flowchart and / or block diagram blocks or multiple blocks.

[0111] The flowchart and / or block diagram in the figure illustrate the possible architecture, functions and operations of the system, method and computer program product according to various embodiments of the present invention. In this regard, each block in the flowchart or block diagram can represent a module, segment or partial instruction, including one or more executable instructions for implementing a specified logical function. In certain alternative embodiments, the functions marked in the block may not appear in the order marked in the figure. For example, two blocks displayed in succession may actually be executed substantially simultaneously, or sometimes the blocks may be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart illustration, as well as the combination of blocks in the block diagram and / or flowchart illustration, can be implemented by a dedicated hardware-based system that can perform specified functions, or implement or execute a combination of dedicated hardware and computer instructions.

[0112] The terms used herein are only used to describe specific embodiments and are not intended to limit the present invention. The singular forms "a, an and the" used herein also include plural forms unless the context clearly indicates otherwise. It should be further understood that the terms used in this specification include and / or contain the presence of specified features, integers, steps, operations, elements and / or components, but do not exclude the presence or increase of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0113] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act that performs the function in combination with the other claim elements as described in the specific claims. The description of the invention is for purposes of illustration and description, but is not intended to be exhaustive or limited to the invention in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the invention. The embodiments of the invention are chosen and described in order to best explain the principles of the invention and the practical application, and to enable those of ordinary skill in the art to understand the various embodiments of the invention, with various modifications as are suited to the particular use contemplated.

[0114] The concepts of the present invention can be summarized in the following terms:

[0115] 1. A computer-implemented method for authenticating and authorizing a user identifier to access a service, wherein the service is protected by an identity access management system, wherein the service is activatable via a service application programming interface, the application programming interface requiring two-factor authorization to initiate execution of the service for the requesting user identifier, wherein the method comprises:

[0116] - receiving, through an application programming interface of the service, a service request and first data of a first authentication method and second data of a second authentication method,

[0117] - using a first authentication method, confirming the correctness of the first data as a first identity passkey,

[0118] - confirming the correctness of second data as a second identity passkey using a second authentication method, wherein the first identity passkey is used as input to the second authentication method, and wherein the second authentication method is different from the first authentication method, and

[0119] -After receiving the first identity passkey and the second identity passkey, execute the service.

[0120] 2. The method of clause 1, wherein the first authentication method is based on a client security certificate, and wherein the second authentication method is based on a security token or an application programming interface key.

[0121] 3. A method according to clause 1 or 2, wherein the first authentication method uses the mTLS standard.

[0122] 4. A method according to any of the preceding clauses, wherein the correctness of the first data and the second data is confirmed by an identity access management system.

[0123] 5. A method according to any of the preceding clauses, wherein confirming the first data and confirming the second data are performed by an independent service that is in communication with the requested service or in communication with the requested service.

[0124] 6. A method according to any of the preceding clauses, wherein the client certificate is from an identity access management system.

[0125] 7. A method according to any of the preceding clauses, wherein the client certificate is generated by the user.

[0126] 8. A method according to any of the preceding clauses, wherein the target service is integrated into a composite service, the security service portion is integrated into the composite service and comprises an mTLS endpoint for the first authentication method.

[0127] 9. The method of clause 8, wherein the security service further comprises an internal security service for authentication via a token or an application programming interface key.

[0128] 10. A method according to any of the preceding clauses, wherein the target service is executed in a cloud computing environment.

[0129] 11. An authentication and authorization system for authenticating and authorizing a user identifier to access a service, wherein the service is protected by an identity access management system, wherein the service can be activated through a service application programming interface, the application programming interface requiring two-factor authorization to begin execution of the service requesting the user identifier, wherein the system comprises:

[0130] - a processor and a memory communicatively coupled to the processor, wherein the memory stores program code portions that, when executed, enable the processor to

[0131] - Receive service requests through the service's application programming interface and

[0132] first data for a first authentication method and

[0133] Second data of the second authentication method.

[0134] - confirming the correctness of the first data as the first identity passkey using the first authentication method,

[0135] - confirming the correctness of second data as a second identity passkey using a second authentication method, wherein the first identity passkey is used as input to the second authentication method, the second authentication method being different from the first authentication method, and

[0136] -After receiving the first identity passkey and the second identity passkey, execute the service.

[0137] 12. The system of clause 11, wherein the first authentication method is based on a client security certificate and the second authentication method is based on a security token or an application programming interface key.

[0138] 13. A system according to clause 11 or 12, wherein the first authentication method uses the mTLS standard.

[0139] 14. The system according to any of clauses 11 to 13, wherein the correctness of the first data and the second data is confirmed by an identity access management system.

[0140] 15. The system according to any of clauses 11 to 14, wherein validating the first data and validating the second data are performed by the requested service or an independent service in communication with the requested service.

[0141] 16. A system according to any of clauses 11 to 15, wherein the client credentials are from an identity access management system.

[0142] 17. A system according to any of clauses 11 to 16, wherein the client certificate is generated by a user.

[0143] 18. The system of clause 11, wherein the target service is integrated into a composite service, the security service portion is integrated into the composite service and includes an mTLS endpoint for the first authorization method.

[0144] 19. The system of clause 18, wherein the security service further comprises an internal security service for authentication via a token or an application programming interface key.

[0145] 20. A computer program product for authenticating and authorizing a user identifier to access a service, wherein the service is protected by an identity access management system, wherein the service is activated by a service application programming interface that requires two-factor authorization in order to initiate execution of the service requesting the user identifier,

[0146] The computer program product includes a computer-readable storage medium containing program instructions, which can be executed by one or more computing systems or controllers to cause one or more computing systems to

[0147] - Receive service requests through the service's application programming interface and

[0148] first data for a first authentication method and

[0149] Second data of the second authentication method.

[0150] - using a first authentication method, confirming the correctness of the first data as a first identity passkey,

[0151] - confirming the correctness of second data as a second identity passkey using a second authentication method, wherein the first identity passkey is used as input to the second authentication method, and wherein the second authentication method is different from the first authentication method, and

[0152] -After receiving the first identity passkey and the second identity passkey, execute the service.

Claims

1. A computer-implemented method for authenticating and authorizing a user identifier to access a service protected by an identity access management system, wherein the service is activated through a service application programming interface, the service application programming interface requiring two-factor authorization to initiate execution of the service for the requesting user identifier, wherein the method comprises: receiving, by one or more processors, a service request and first data for a first authentication method and second data for a second authentication method, wherein the service request is connected to an application programming interface of the service; confirming, by the one or more processors, the correctness of the first data as a first identity pass key using the first authentication method; validating, by the one or more processors, the correctness of the second data as a second identity pass key using the second authentication method, wherein the validated first identity pass key is included as an input to the second authentication method, and the second authentication method is different from the first authentication method; as well as The service is performed by the one or more processors in response to confirming correctness of the received first identity passkey and the second identity passkey.

2. The method of claim 1, wherein the first authentication method and the second authentication method are selected from the group consisting of a client security certificate, a security token, and an application programming interface key, and wherein the first authentication method is different from the second authentication method.

3. The method of claim 1 or 2, wherein the first authentication method uses the Mutual Transport Layer Security (mTLS) standard. 4 . The method according to claim 1 , wherein the confirmation of the correctness of the first data and the second data is performed by an identity access management system.

5. The method according to one of claims 1 to 4, wherein the confirmation of the correctness of the first data and the confirmation of the correctness of the second data are performed by selection from the group consisting of the requested service and a separate service in communication with the requested service.

6. The method according to any one of claims 1 to 5, wherein the client security certificate comes from an identity access management system and is used as an identity pass key. The method of claim 6 , wherein the client security certificate is generated by a user.

8. The method according to any one of claims 1 to 7, wherein the requested service is a combined service, and wherein: A security service is integrated into the composite service and includes an mTLS endpoint for the first authorization method.

9. The method of claim 8, wherein the security service further comprises an internal security service for using authentication selected from the group consisting of a token and an application programming interface key.

10. The method according to any one of claims 1 to 9, wherein the requested service is performed in a cloud computing environment.

11. An authentication and authorization system for authenticating and authorizing a user identifier to access a service protected by an identity access management system, wherein the service is activated through a service application programming interface, the application programming interface requiring two-factor authorization to initiate execution of the service for the requesting user identifier, the system comprising: one or more computer processors; One or more computer-readable storage media communicatively coupled to the one or more processors, wherein the one or more computer-readable storage media store program code portions that, when executed, enable the one or more processors to: receiving a service request and first data for a first authentication method and second data for a second authentication method, wherein the service request is connected to an application programming interface of the service; confirming the correctness of the first data as a first identity passkey using the first authentication method; validating the correctness of the second data as a second identity pass key using the second authentication method, wherein the validated first identity pass key is included as an input to the second authentication method, and the second authentication method is different from the first authentication method; as well as In response to the confirmed correctness of the first identity passkey and the second identity passkey, the service is performed.

12. The system of claim 11, wherein the first authentication method and the second authentication method are selected from the group consisting of a client security certificate, a security token, and an application programming interface key, and wherein the first authentication method is different from the second authentication method.

13. The system of claim 11 or 12, wherein the first authentication method uses the Mutual Transport Layer Security (mTLS) standard.

14. The system according to any one of claims 11 to 13, wherein the correctness of the first data and the second data is confirmed by the identity access management system.

15. The system according to any one of claims 11 to 14, wherein the confirmation of the correctness of the first data and the second data is performed by selection from the group consisting of the requested service and a separate service in communication with the requested service.

16. The system according to any one of claims 11 to 15, wherein: The client security certificate comes from the identity access management system and is used as the identity pass key.

17. The system of claim 16, wherein the client certificate is generated by a user.

18. The system according to any one of claims 11 to 17, wherein the requested service is a composite service, and wherein: A security service is integrated into the composite service and includes an mTLS endpoint for the first authorization method.

19. The system of claim 18, wherein the security service further comprises an internal security service for authentication via a token or an application programming interface key.

20. A computer program product for authenticating and authorizing a user identifier to access a service, wherein the service is secured by an identity access management system and the service is activated by a service application programming interface, the application programming interface requiring two-factor authorization to initiate execution of the service for the requesting user identifier, the computer program product comprising: A computer readable storage medium containing program instructions executable by one or more computer processors to enable the one or more computer processors to: receiving a service request and first data for a first authentication method and second data for a second authentication method, wherein the service request is connected to an application programming interface of the service; Using the first authentication method, confirming the correctness of the first data as a first identity passkey; validating the correctness of the second data as a second identity pass key using the second authentication method, wherein the validated first identity pass key is included as an input to the second authentication method, and the second authentication method is different from the first authentication method; as well as In response to confirming the correctness of the received first identity passkey and second identity passkey, performing the service.