Method and apparatus for providing cloud service-related credential service
The cloud service credentialing service addresses the challenges of credential key leakage and temporary credential management by issuing temporary credentials and distributing credentialing tasks, enhancing security and convenience while maintaining system balance.
Patent Information
- Application Number
- PCT/KR2024/007157
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-31
- Filing Date
- 2024-05-27
- Publication Date
- 2024-12-05
AI Technical Summary
Developers face challenges in securely managing and using cloud service credentials, particularly due to the risk of credential key leakage when hard-coding permanent keys into source code, and the burden of obtaining temporary credentials for API calls, which can lead to unintentional errors and security breaches.
A method and device provide a cloud service-related credentialing service that issues temporary credentials on behalf of users, allowing selection from multiple cloud services, managing credential validity periods, and distributing credentialing tasks efficiently across modules to prevent load imbalances and hard-coding risks.
This solution enhances security by eliminating hard-coding risks, simplifies credential management, and reduces the burden on developers by providing temporary credentials for cloud service APIs, thereby strengthening security and improving user convenience while maintaining system load balance.
Smart Images

Figure KR2024007157_05122024_PF_FP_ABST
Abstract
Description
Method and device for providing cloud service-related credential services
[0001] The present disclosure relates to a method and device for providing a credential service related to cloud services. More specifically, the present disclosure relates to a method and device for providing a credential service that must precede a call to an Application Programming Interface (API) provided as part of a cloud service.
[0002] Cloud service providers offer a variety of APIs, allowing users to easily implement common, essential functions required for software development simply by calling the API. Calling these APIs requires credentials. Developers often embed these credentials into their program source code. In other words, credential keys are often "hard-coded" into the source code.
[0003] Embedding credentials for API calls into the source code can prevent unintended errors or failures during the credential verification process. However, it also raises the possibility of leaking credentials issued by cloud service providers for specific users. For example, source code with hard-coded credentials could be exposed to an unspecified number of people for contributions to open source projects.
[0004] Temporary credentials, valid only temporarily, could prevent the continued use of leaked keys. However, obtaining temporary credentials from each cloud service provider to utilize their APIs would impose an additional burden on developers. This burden would likely lead developers to avoid temporary credentials, preferring instead to hard-code permanent credentials and the resulting credential keys into their source code.
[0005] Therefore, there is a need to provide a new service that can receive and process temporary credentials for API calls from various cloud service providers.
[0006] A technical problem to be solved through some embodiments of the present disclosure is to provide a method and device that can provide a cloud service-related credential service that issues credentials for a third-party cloud service on behalf of a user in the company's cloud service.
[0007] The technical problem to be solved through some embodiments of the present disclosure is to provide a method and device for providing a cloud service-related credential service that can provide temporary credentials for a third-party cloud for a desired period of time to a user of the company's cloud service when the user must use a third-party cloud service while using the company's cloud service.
[0008] Another technical problem to be solved through some embodiments of the present disclosure is to provide a method and device for providing a cloud service-related credential service that can prevent the load of each module or system by efficiently distributing the roles of modules or systems required for performing credentialing.
[0009] The technical problems of the present disclosure are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art of the present disclosure from the description below.
[0010] In order to solve the above technical problem, a method for providing a cloud service-related credential service according to an embodiment of the present disclosure may include the steps of: transmitting, to a user terminal, data of a request page including a cloud service selection field for selecting one cloud service from a list of a plurality of cloud services including a second cloud service and a third cloud service; receiving, from the user terminal, a request for issuance of a temporary key for credentials for calling an API of the second cloud service selected in the cloud service selection field; transmitting, in response to receiving the request for issuance of the temporary key, an account issuance request signal to a system of the second cloud service; receiving, in response to transmitting the account issuance request signal, credential key information for a first account issued to an organization operating the computing system from a system of the first cloud service; and transmitting, to the user terminal, the credential key information in response to the request for issuance of the temporary key.
[0011] As one embodiment, the request page may further include a field for entering a validity period of the API call credentials, and the step of transmitting the account issuance request signal may include a step of transmitting an account issuance request signal for requesting issuance of a temporary account that is valid for a period corresponding to the validity period of the API call credentials.
[0012] As one embodiment, the step of transmitting an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the API call credentials may include the step of transmitting a temporary account issuance request signal when the validity period entered through the request page corresponds to the validity period of a temporary account supported by the second cloud service.
[0013] In one embodiment, the step of transmitting an account issuance request signal requesting issuance of a temporary account valid for a period corresponding to the validity period of the API call credentials may include a step of transmitting a permanent account issuance request signal when the validity period entered through the request page does not correspond to the validity period of a temporary account supported by the second cloud service, and the step of transmitting the key information may include a step of transmitting an account deletion request signal to a system of the second cloud service when the validity period of the API call credentials expires.
[0014] As one embodiment, the request page may further include a field for inputting a validity period of the API call credentials, the step of transmitting the account issuance request signal may include a step of transmitting a permanent account issuance request signal, and the step of transmitting the key information may include a step of transmitting an account deletion request signal to the system of the second cloud service when the validity period of the API call credentials expires.
[0015] In order to solve the above technical problem, according to another embodiment of the present disclosure, a method for providing a cloud service-related credential service is provided, which is performed by a cloud service providing system including an ID Provider (IDP) module, an Identity and Access Management (IAM) module, and a first system, the method comprising: receiving, from a user terminal, a request for issuing an authentication token for authentication of the cloud service, wherein the authentication token issuance request includes an access key issued by the IAM module and an IDP token issued by the IDP module and information on the validity period of a temporary key; transmitting, in response to receiving the request for issuing the authentication token, a verification request for the IDP token to the IDP module; receiving a verification result for the IDP token from the IDP module; and, if the verification result is a verification success, the first system issues an authentication token and transmits the issued authentication token to the user terminal, and matches and stores the access key, the validity period information, and the authentication token included in the request for issuing the authentication token; and transmitting, by the first system, from an application, a credential for calling an API serviced by the cloud service. The method may include receiving a request for issuance of a temporary key for credentials, wherein the request for issuance of the temporary key includes the authentication token, and the first system may perform authentication for the application using the authentication token included in the request for issuance of the temporary key, and when the authentication passes, issuing a temporary key having a validity period according to validity period information stored corresponding to the authentication token, and transmitting the issued temporary key to the application.
[0016] In order to solve the above technical problem, a cloud service-related credential service providing system according to another embodiment of the present disclosure may include one or more processors and a memory storing instructions. At this time, the one or more processors may, by executing the stored instructions, perform the following operations: transmitting, to a user terminal, data of a request page including a cloud service selection field for selecting one cloud service from a list of multiple cloud services including a second cloud service and a third cloud service; receiving, from the user terminal, a request for issuance of a temporary key for credentials for calling an API of the second cloud service selected in the cloud service selection field; transmitting, in response to receiving the request for issuance of the temporary key, an account issuance request signal to a system of the second cloud service; receiving, in response to transmitting the account issuance request signal, credential key information for a first account issued to an organization operating the computing system from a system of the second cloud service; and transmitting, in response to the request for issuance of the temporary key, the credential key information to the user terminal.
[0017] In order to solve the above technical problem, according to another embodiment of the present disclosure, a computer program is coupled to a computing device to provide a cloud service-related credential service, and is stored in a computer-readable recording medium to execute the steps of: transmitting data of a request page including a cloud service selection field for selecting one cloud service from a list of a plurality of cloud services including a second cloud service and a third cloud service to a user terminal; receiving, from the user terminal, a request for issuance of a temporary key for credentials for calling an API serviced by the second cloud service selected in the cloud service selection field; transmitting, in response to receiving the request for issuance of the temporary key, a signal for requesting account issuance to a system of the second cloud service; receiving, in response to transmitting the signal for issuing the account, key information for credentials for a first account issued to an organization operating the computing system, from a system of the second cloud service; and transmitting, in response to the request for issuance of the temporary key, the key information for credentials to the user terminal.
[0018] FIG. 1 and FIG. 2 are configuration diagrams of a cloud service-related credential service provision system according to one embodiment of the present disclosure.
[0019] FIG. 3 is a flowchart of a method for providing a cloud service-related credential service according to another embodiment of the present disclosure.
[0020] FIG. 4 is a diagram illustrating an exemplary temporary key issuance request page for credentials for calling an API, which may be displayed on a user terminal in some embodiments of the present disclosure.
[0021] FIG. 5 is a signal flow diagram of a method for providing a cloud service-related credential service described with reference to FIG. 3.
[0022] FIG. 6 is a diagram illustrating a temporary key issuance result guidance message that may be displayed on a user terminal in some embodiments of the present disclosure.
[0023] FIG. 7 is a diagram illustrating an exemplary temporary key issuance request page for credentials for calling an API that may be displayed on a user terminal in some embodiments of the present disclosure.
[0024] FIG. 8 is a detailed flowchart for explaining in detail some operations of the cloud service-related credential service provision method described with reference to FIG. 3.
[0025] FIG. 9 is a flowchart of a method for providing a cloud service-related credential service according to another embodiment of the present disclosure.
[0026] FIG. 10 and FIG. 11 are signal flow diagrams of a method for providing a cloud service-related credential service described with reference to FIG. 9.
[0027] FIG. 12 is a diagram of an exemplary computing system that can implement devices according to various embodiments of the present disclosure.
[0028] Hereinafter, preferred embodiments of the present disclosure will be described in detail with reference to the attached drawings. The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described in detail below together with the attached drawings. However, the technical idea of the present disclosure is not limited to the following embodiments and may be implemented in various different forms. The following embodiments are provided only to complete the technical idea of the present disclosure and to fully inform those skilled in the art of the present disclosure of the scope of the present disclosure, and the technical idea of the present disclosure is defined only by the scope of the claims.
[0029] When assigning reference numerals to components in each drawing, it should be noted that identical components are assigned the same numerals whenever possible, even if they appear on different drawings. Furthermore, when describing the present disclosure, if a detailed description of a related known configuration or function is deemed likely to obscure the gist of the present disclosure, such detailed description will be omitted.
[0030] Unless otherwise defined, all terms (including technical and scientific terms) used herein may be used in the same sense as commonly understood by those of ordinary skill in the art to which this disclosure pertains. Furthermore, terms defined in commonly used dictionaries are not to be interpreted ideally or excessively unless explicitly and specifically defined otherwise. The terminology used herein is for the purpose of describing embodiments and is not intended to limit the disclosure. In this specification, singular forms also include plural forms, unless specifically stated otherwise.
[0031] Additionally, terms such as first, second, A, B, (a), (b), etc. may be used to describe components of the present disclosure. These terms are only intended to distinguish the components from other components, and the nature, order, or sequence of the components are not limited by the terms. When a component is described as being "connected," "coupled," or "connected" to another component, it should be understood that the component may be directly connected or connected to the other component, but another component may also be "connected," "coupled," or "connected" between each component.
[0032] As used herein, the terms “comprises” and / or “comprising” do not exclude the presence or addition of one or more other components, steps, operations and / or elements.
[0033] Below, various embodiments of the present disclosure for solving the technical problems described above will be described.
[0034] Hereinafter, with reference to FIGS. 1 and 2, the configuration and operation of a cloud service-related credential service provision system according to one embodiment of the present disclosure will be described. FIG. 1 is a configuration diagram of a system in which the cloud service provision system acts as a credential provider. Hereinafter, the "cloud service-related credential service provision system" will be abbreviated as "service provision system."
[0035] Referring to FIG. 1, the service providing system according to the present embodiment may include a first cloud service providing system (10), a second cloud service providing system (20-1), a third cloud service providing system (20-2), a user terminal (30), and a network (40).
[0036] The first cloud service provision system (10) can receive a request for issuance of a temporary key for credentials for calling an API serviced by a cloud service from a user terminal (30). Hereinafter, for convenience of understanding, the term "API serviced by a cloud service" will be abbreviated as "cloud API."
[0037] At this time, the issuance request may include selection information for either the second cloud service provision system (20-1) or the third cloud service provision system (20-2). For ease of understanding, the following description assumes that the second cloud service provision system (20-1) has been selected.
[0038] The first cloud service providing system (10) can, in response to the issuance request, transmit an account issuance request signal to the second cloud service system (20-1), and receive, from the second cloud service system (20-1), key information for credentials for the first account issued to the organization operating the first cloud service providing system (10). In addition, the first cloud service providing system (10) can transmit the key information for credentials to the user terminal (30) in response to the request for issuance of the temporary key.
[0039] The first cloud service provision system (10) may also be understood as acting as an agent for a temporary key issuance request from a user who wishes to utilize the API of the second cloud service system (20-1). As described above, the second cloud service system (20-1) issues the first account to the organization operating the first cloud service provision system (10), and does not issue the first account to the user. In other words, the user can utilize the API provided by the second cloud service system (20-1) without registering with the second cloud service system (20-1).
[0040] The service provision system according to this embodiment can provide groundbreaking user convenience by allowing the APIs of various CSP operators to be utilized without a membership registration process for each CSP operator.
[0041] In addition, the service provision system according to the present embodiment can solve the problem of hardcoding the credential key described above to some extent by issuing a credential key required for API calls of various CSP operators in the form of a temporary key.
[0042] The first cloud service providing system (10) may be a system that not only issues temporary keys for credentials for cloud APIs, but also provides its own Cloud Service Provider (CSP) service. Of course, in some embodiments, the first cloud service providing system (10) may be a system that only performs the temporary key issuance service and does not perform its own CSP service.
[0043] The second cloud service providing system (20-1) and the third cloud service providing system (20-2) refer to cloud service providing systems that are distinct from the first cloud service providing system (10). For example, when the first cloud service providing system (10) is said to be a system of the first service provider, the second cloud service providing system (20-1) may be a system of a second cloud service provider different from the first service provider, and the third cloud service providing system (20-2) may be a system of a third cloud service provider different from the first service provider.
[0044] The network (40) provides a wired / wireless communication means for data transmission between the first cloud service providing system (10) and the second cloud service providing system (20-1), or between the first cloud service providing system (10) and the user terminal (30). The network (40) may include a local area network (LAN), a wireless local area network (WLAN), Wi-Fi, Bluetooth, 4G, 5G, or other wired / wireless communication means. Since specific technical details regarding the network (400) are widely known in the art, a description thereof is omitted herein.
[0045] In this embodiment, the first cloud service provision system (10) requests the issuance of a temporary key for account credentials with a set expiration date and transmits it to the user only when the user needs to access the second cloud service provision system (20-1). Therefore, according to this embodiment, security is enhanced by eliminating the need for hardcoding in source code or configuration files, and accounts for other cloud services can be managed within a single cloud service.
[0046] It has been explained that the cloud service providing system (10) of the service providing system according to the present embodiment may be a system that provides a CSP service on its own, as well as a service that issues temporary keys for credentials for API calls. The cloud service providing system (10) may provide the service of issuing temporary keys for credentials for API calls through a separate module, rather than through core modules related to the overall CSP service, such as an ID provider module (IDP) and an ID and access management module (IAM). As a result, the cloud service providing system (10) can minimize the impact of the service issuing temporary keys for credentials for API calls on the CSP service.
[0047] The above-described cloud service provision system (10) may include an ID Provider (IDP) module, an Identity and Access Management (IAM) module, and a first system.
[0048] The cloud service provision system (10) can receive, from a user terminal, a request for issuing an authentication token for authentication of the cloud service. The request for issuing the authentication token can include an access key issued by the IAM module, an IDP token issued by the IDP module, and information on the validity period of a temporary key.
[0049] In addition, the cloud service providing system (10) may, in response to receiving the authentication token issuance request, transmit a verification request for the IDP token to the IDP module. The cloud service providing system (10) may receive a verification result for the IDP token from the IDP module, and if the verification result is a verification success, the first system may issue an authentication token and transmit the issued authentication token to the user terminal, and may match and store the access key, the validity period information, and the authentication token included in the authentication token issuance request.
[0050] Next, the first system of the cloud service provision system (10) may receive, from an application, a request for issuance of a temporary key for credentials for calling an API serviced by the cloud service. The request for issuance of the temporary key may include the authentication token. In addition, the first system may perform credentials for the application using the authentication token included in the request for issuance of the temporary key. When the credentials are passed, the first system may issue a temporary key having a validity period according to validity period information stored corresponding to the authentication token. The first system may transmit the issued temporary key to the application.
[0051] In some embodiments, the first system may be a security key management system (KMS). The first system may provide a service for easily generating and securely storing / managing encryption keys to safely protect important application data. Users may encrypt / decrypt data using encryption keys, and the encryption keys may be reliably managed using a centralized, hierarchically encrypted encryption key system. Furthermore, the first system may protect data from cryptographic threats through key lifecycle management.
[0052] The above first system may be a system that provides a service introduced through, for example, “https: / www.samsungsds.com / kr / security-key-management-service / security-key-management-service.html”.
[0053] By having a security key management system that performs key management functions but is not a core system that affects the overall CSP service, perform credential authentication and temporary key issuance operations, the system-wide load balance that provides the CSP service can be maintained while achieving the effect of having an optimal module perform operations according to embodiments of the present disclosure.
[0054] Figure 2 is a diagram illustrating a detailed configuration of a cloud service-related credential service provision system. Referring to Figure 2, the relationships between modules or systems included in the first cloud service provision system (10) are illustrated. Detailed operations between modules or systems are described later in Figure 5, and the roles of each module or system are described below.
[0055] The ID Provider (IDP, hereinafter referred to as 'IDP') module (120) is a system that creates, stores, and manages a user's ID and provides a user authentication service using the first cloud service provision system (10).
[0056] The service console provision system (140) is a middleware that executes an application running on the first cloud service provision system (10) to perform necessary functions and transmits the results to a web server, and transmits a request for issuing a temporary key for the user's second cloud service provision system (20-1) to the first system (130).
[0057] Since the Identity and Access Management (IAM, hereinafter referred to as 'IAM') module (110) stores the policies registered in the first cloud service and the permissions of each user, the first cloud service providing system (10) can request the second cloud service providing system (20-1) to issue a temporary key according to the policies and permissions registered in the IAM module (110).
[0058] The first system (130) verifies a token containing the user's account information issued by the IDP module (120) through the authentication module (132a), and when the verification is successful, requests the second cloud service providing system (20-1) to issue a temporary key credential information for accessing the second cloud service providing system (20-1), receives a temporary account with a set validity period, and transmits credential information for the issued temporary account to the user terminal (30).
[0059] The operation of the service provision system according to this embodiment can be understood in more detail by referring to other embodiments described below. Furthermore, the technical concepts understood through the above-described embodiments of the service provision system according to this embodiment can be reflected in other embodiments described below, even if not specifically stated otherwise.
[0060] Hereinafter, a method for providing a cloud service-related credential service according to another embodiment of the present disclosure will be described with reference to FIGS. 3 to 8. Hereinafter, for ease of understanding, the term "method for providing a cloud service-related credential service" will be abbreviated as "service providing method." The service providing method according to the present embodiment may be performed by a computing device. Furthermore, the service providing method according to the present embodiment may have some operations performed by a first computing device, and the remaining operations performed by a second computing device. For example, some operations of the service providing method according to the present embodiment may be performed by an on-premise physical server, and the remaining operations may be performed by a cloud compute instance. Hereinafter, if the performing entity of each operation is omitted, it will be understood that the performing entity is the computing system.
[0061] First, a service provision method according to the present embodiment will be described with reference to FIG. 3.
[0062] First, the computing system can transmit data of a request page including a cloud service selection field to a user terminal (30) so that one cloud service can be selected from a list of multiple cloud services including a second cloud service and a third cloud service (S300). Referring to FIG. 4, in the transmitted request page, the first cloud service providing system (10) can receive input of a type (401) of a cloud service provider (CSP, hereinafter referred to as “CSP”), an access key (402, Access Key), and a secret key (403, Secret Key) from the user through the service console providing system (140).
[0063] The CSP type may include any type of cloud service, including a second cloud service and a third cloud service, distinct from the first cloud service. In the area for entering the access key (402) and secret key (403), the user enters the access key and secret key of an account previously created and authorized for the second cloud service provision system (20-1). It should be noted that this is distinct from the credential information issued by the second cloud service provision system (20-1) for a temporary account.
[0064] Thereafter, when the user enters information about the type of CSP, access key, and secret key and clicks the confirmation button (404), the first cloud service provision system (10) receives a request for issuance of a temporary key for credentials for calling the second cloud service API from the user terminal (30) (S310).
[0065] Next, in response to receiving a request for issuance of a temporary key from a user terminal (30), the first cloud service providing system (10) transmits an account issuance request signal to the second cloud service providing system (20-1) (S320). Here, the account for which issuance is requested is distinct from an account previously created by the user and having authority over the second cloud service providing system (20-1), and refers to an account temporarily issued by the second cloud service providing system (20-1) to the first cloud service providing system (10).
[0066] Before the first cloud service provision system (10) transmits an account issuance request signal to the second cloud service provision system (20-1), an API requesting temporary key issuance is transmitted within the first cloud service provision system (10) and user authentication using the first cloud service is performed. A detailed description thereof will be provided later with reference to FIG. 5.
[0067] Next, in response to the transmission of the account issuance request signal, the first cloud service providing system (10) receives, from the second cloud service providing system (20-1), credential information for a temporary account issued to the institution operating the first cloud service providing system (10) (S330).
[0068] Finally, the first cloud service provision system (10) transmits credential information for a temporary account in response to a request for issuance of a temporary key to the user terminal (S340).
[0069] Hereinafter, a method for providing a cloud service-related credential service according to one embodiment of the present disclosure will be described with reference to FIG. 5. FIG. 5 is a signal flow diagram of the method for providing a cloud service-related credential service described with reference to FIG. 3.
[0070] As a preliminary task before performing the series of tasks illustrated in FIG. 5, a user creates an authorized account by specifying the necessary permissions for a second cloud service to which the user intends to access through the first cloud service provision system (10), and sets key information for authentication of the user's second cloud service account in the first system (130). The key information for authentication includes the access key and secret key of the account created by the first cloud service that can access the second cloud service. The following describes a method for providing a cloud service-related authentication service, assuming that the above preliminary tasks have been completed.
[0071] The process of providing a cloud service-related credential service can be broadly divided into a process in which a first cloud service provision system (10) authenticates a user and verifies authority, and a process in which a second cloud service requests issuance of credentials and transmits key information for credentials issued for a temporary account to the user (application).
[0072] Below, the process for user authentication and authorization confirmation of the first cloud service provision system (10) that acts as an agent for requesting issuance of credentials will be described in detail.
[0073] When the first cloud service provision system (10) receives a request for issuance of a temporary key for authentication for a second cloud service from a user terminal (30), the application requests the IDP module to issue an IDP token required for using a cloud API within the first cloud service provision system (10) (S501). The IDP token is a token issued by the IDP module for using the first cloud service provision system (10) and includes account information of a user using the API.
[0074] When the application receives an IDP token from the IDP module (S502), the application sends an API requesting the service console provider system to issue a temporary key for accessing the second cloud service (S503). At this time, information regarding the validity period of the credentials for the API call entered by the user may also be transmitted.
[0075] Thereafter, the service console provision system internally verifies the user's authentication and authorization (S504) and requests the first system to issue a temporary key for authentication (S905). At this time, the request for issuance of a temporary key for authentication may be made while transmitting an IDP token issued by the IDP module. The first system (130) may be a Key Management Service (KMS, hereinafter referred to as "KMS") system.
[0076] If the service console provisioning system internally successfully authenticates the user, the management module can log in using the IDP token that successfully authenticated the authentication module installed within the authentication engine.
[0077] Thereafter, the authentication module within the first system requests verification of the IDP token for the requested login information value from the IDP module (S506). Specifically, the authentication module can perform authentication using the IDP module and the logged-in authentication information. The authentication method here may employ the JWT (JSON Web Token) authentication method, but is not limited thereto. During the authentication process, verification may also be performed to verify whether the user has permission to use the services provided by the first cloud service, including user authentication. For example, a verification may be performed to verify that a logged-in user has permission to read but not modify services provided by the first cloud service.
[0078] If the authentication module within System 1 successfully verifies the IDP token containing the login information, the IDP module confirms the successful verification with the authentication module within System 1 and notifies the authentication module within System 1 (S907). The authentication module then transmits information about the successful user authentication to the management module.
[0079] Thereafter, the management module within the first system requests the IAM module to issue a temporary key for the second cloud service provision system (20-1) (S908). At this time, the policies and roles for the second cloud service registered in the IAM module can be verified, and based on the verified policies and roles, the first cloud service provision system (10) can request the second cloud service provision system (20-1) to issue key information for authentication.
[0080] Through the above procedure, authentication and authorization for users logged into the first cloud service can be verified.
[0081] Below, a process in which a first cloud service provision system (10) requests a second cloud service to issue credentials and transmits key information for the issued credentials to a user (application) will be described.
[0082] First, the authentication engine within the first system requests account issuance from the second cloud service provider (20-1). In response to the account issuance request, the second cloud service provider (20-1) issues a temporary account to the first cloud service provider. Thereafter, the authentication engine requests the issuance of credential key information for the issued temporary account (S509). The credential key information for the temporary account may include information regarding an access key and a secret key for accessing the second cloud service provider (20-2).
[0083] Thereafter, the second cloud service providing system (20-1) performs authentication and authorization verification for the temporary account with the first cloud service provider (S510). If the authentication and authorization verification are successful, the second cloud service providing system (20-1) transmits credential key information for the temporary account to the authentication engine (S511). Fig. 6 is a diagram illustrating a temporary key issuance result guidance message that can be displayed on a user terminal. As illustrated in Fig. 6, the credential information for the temporary account includes a cloud service provider (61) such as AWS, Azure, and GCP, an API call credential expiration date (62), an access key (63), and a secret key (64). Here, the access key and secret key included in the key information for credentials are the access key and secret key for the temporary account issued by the second cloud service providing system (20-1) to the first cloud service provider, and are clearly distinguished from the access key (402) and secret key (403) of the account with authority for the second cloud service providing system (20-1) created in advance by the user as discussed above.
[0084] When the authentication engine (132) receives key information for credentials for a temporary account, the first system transmits it to the application (S512).
[0085] The method for providing a cloud service-related credential service has been described above, through a process in which the first cloud service providing system (10) authenticates a user and confirms authority, and a process in which the second cloud service requests credential issuance and transmits credential key information issued for a temporary account to the user (application). In this embodiment, the first cloud service providing system (10) acts as an agent for the user to request credential issuance for the second cloud service, and only when the user needs to access the second cloud service, the first cloud service providing system (10) creates a temporary account and issues credential key information for the temporary account. Therefore, according to this embodiment, since the access key and secret key for the account of the first cloud service do not need to be hard-coded in the source code or configuration file, the leakage of credential key information can be prevented, and convenience for the user when using the cloud service can be increased.
[0086] Hereinafter, some operations of a method for providing a cloud service-related credential service will be described in detail with reference to FIGS. 7 and 8.
[0087] FIG. 7 is a drawing of a request page for receiving input of a credential validity period, which is a console screen displayed on a user terminal (30). Referring to FIG. 7, in the transmitted request page, the first cloud service provision system (10) can receive input from the user, through the service console provision system (140), of the type (71) of a cloud service provider (CSP, hereinafter referred to as "CSP"), an access key (72, Access Key), a secret key (73, Secret Key), and an API call credential validity period (74).
[0088] In the area where the access key (72) and secret key (73) are input, the access key and secret key of an account with authority for the second cloud service provision system (20-1) that the user has previously created can be input. In addition, by setting a validity period (74) for the credential for API calls, when the validity period expires, the credential key information for the temporary account issued by the second cloud service to the first cloud service provider can be deleted.
[0089] Referring to FIG. 8 below, a method for providing a cloud service-related credential service according to one embodiment of the present disclosure will be described. FIG. 8 is a detailed flowchart illustrating some operations of the method for providing a cloud service-related credential service described with reference to FIG. 3.
[0090] In one embodiment, the first cloud service providing system (10) may receive the validity period (74) of credentials for API calls from the user terminal (30) as shown in FIG. 7 (S321). The first cloud service providing system (10) may transmit a temporary account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the credentials for API calls input to the second cloud service providing system (20-1).
[0091] "Corresponding" to the validity period of the credentials for the API call entered here means that the validity period entered by the user is exactly the same as the validity period for an account that the second cloud service providing system (20-2) can provide, or is within a predetermined period of time. For example, if the validity period entered by the user is '15 days,' the first cloud service providing system (10) can transmit an account issuance request signal requesting the issuance of a temporary account that is valid for a period of '15 days.'
[0092] In another embodiment, the first cloud service providing system (10) may receive the validity period of credentials for API calls from the user terminal (30) as shown in FIG. 7 (S321). In this case, if the entered validity period corresponds to the validity period of a temporary account supported by the second cloud service, the first cloud service providing system (10) may transmit a temporary account issuance request signal to the second cloud service providing system (20-1) according to the entered validity period (S324).
[0093] For example, if the validity period entered by the user is '15 days' and the second cloud service providing system (20-1) can create a temporary account for '15 days', the first cloud service providing system (10) can transmit an account issuance request signal requesting the issuance of a temporary account valid for a period of '15 days'. In this case, since the validity period desired by the user and the service period of the cloud service provided by the second cloud service providing system (20-1) correspond, the first cloud service providing system (10) does not need to transmit a separate deletion request for the temporary account to the second cloud service providing system (20-1).
[0094] In this embodiment, the first cloud service providing system (10) issues a temporary account for the second cloud service and credential key information for the temporary account according to the validity period entered by the user. Therefore, according to this embodiment, the user does not need to create a separate account for the second cloud service, thereby increasing the usability of the cloud service for the user. In addition, since the created account is granted temporariness, the access key and secret key for the account for the first cloud service do not need to be hard-coded in the source code or configuration file, thereby preventing the leakage of credential key information. In addition, the use of the temporary account and credential key information for the temporary account by others other than the cloud service user who is issued the account can be restricted, thereby enhancing the security of the cloud service.
[0095] In another embodiment, the first cloud service providing system (10) may receive the validity period of credentials for API calls from the user terminal (30) as shown in FIG. 7 (S321). If the entered validity period does not correspond to the validity period of a temporary account supported by the second cloud service, the first cloud service providing system (10) may transmit a permanent account issuance request signal to the second cloud service providing system (20-1) (S323).
[0096] For example, if the validity period entered by the user is '18 months' and the maximum period for which the second cloud service providing system (20-1) can provide temporary credentials is '12 months', the first cloud service providing system (10) can transmit a permanent account issuance request signal to the second cloud service providing system (20-1). In this case, in order to prevent a situation in which the credentials for the account are valid beyond the validity period entered by the user, the first cloud service providing system (10) can transmit a deletion request signal for the created permanent account to the second cloud service providing system (20-1) when the validity period entered by the user expires.
[0097] Even if the validity period entered by the user does not correspond to the validity period of a temporary account supported by the second cloud service, the first cloud service providing system (10) manages an account that can access the second cloud service on behalf of the user based on the validity period entered by the user, thereby improving convenience and usability when the user uses the cloud service.
[0098] In another embodiment, the first cloud service providing system (10) may receive the validity period of credentials for API calls from the user terminal (30). Accordingly, the first cloud service providing system (10) may request the second cloud service providing system (20-1) to issue a permanent account. After the permanent account is issued, the first cloud service providing system (10) may request the second cloud service providing system (20-1) to delete the created permanent account when the validity period of the credentials for API calls entered by the user expires. In the present embodiment, the first cloud service providing system (10) may create a permanent account regardless of the validity period entered by the user and delete the account when the validity period expires. Therefore, according to the present embodiment, the first cloud service providing system (10) may manage accounts uniformly, thereby increasing convenience in account management.
[0099] Hereinafter, with reference to FIGS. 9 to 11, a method for providing a cloud service-related credential service according to another embodiment will be described.
[0100] FIG. 9 is a flowchart of a method for providing a cloud service-related credential service, and FIGS. 10 and 11 are signal flowcharts of the method for providing a cloud service-related credential service described with reference to FIG. 9.
[0101] Since the configuration of the cloud service provision system is the same as the detailed configuration of the first cloud service provision system (10) illustrated in FIG. 2, a method for providing and using a temporary key for authentication within the cloud service provision system will be described with reference to the configuration illustrated in FIG. 2.
[0102] Referring to FIG. 9, the service providing system according to the present embodiment can receive, from a user terminal, a request for issuing an authentication token for authentication of a cloud service through the first cloud service providing system (10) (S800). At this time, the request for issuing an authentication token can include an access key issued by the IAM module (110), an IDP token issued by the IDP module (120), and information on the validity period of a temporary key. The above access key is an access key of an account with authority for the first cloud service providing system (20-1) created by the user in advance, and is distinct from a temporary key.
[0103] Thereafter, the first system (130) within the first cloud service provision system (10) can, in response to receiving the authentication token issuance request, transmit a verification request for the IDP token to the IDP module (S810).
[0104] Thereafter, the first system (130) receives a verification result for the IDP token from the IDP module, and if the verification result is a success, the first system (130) issues an authentication token, transmits the issued authentication token to the user terminal, and matches and stores the access key, expiration date information, and authentication token included in the authentication token issuance request in the key storage space (132b) within the first system (130) (S820).
[0105] Next, the first system (130) may receive a request for issuance of a temporary key for credentials for calling a cloud API from an application (S830). At this time, the request for issuance of the temporary key may include an authentication token issued by the first system (130). The temporary key may include an access key and a secret key for accessing the first cloud service, along with a set validity period for the temporary key.
[0106] Finally, using the authentication token included in the request for issuing a temporary key of the first system (130), authentication for the application is performed, and when the authentication is passed, a temporary key having a validity period according to the validity period information stored corresponding to the authentication token is issued, and the issued temporary key can be transmitted to the application (S840).
[0107] Hereinafter, with reference to FIGS. 10 and 11, a method for providing a cloud service-related credential service according to the embodiment of FIG. 9 will be described.
[0108] First, referring to Figure 10, the IAM module receives a request from a user terminal to issue an access key and secret key for access to the cloud service provider system (S901). The access key and secret key are required to authenticate the user as a cloud service user. After authenticating the user as a cloud service user, an IDP token for API calls and use can be issued.
[0109] When the IAM module issues an access key and secret key to a user terminal (S902), the IDP module receives an IDP token issuance request from the user terminal (S903). An IDP token is required to use the API of the cloud service provider system, and contains the account information of the user using the API.
[0110] When the IDP module issues an IDP token to a user terminal (S904), the service console providing system receives an authentication token issuance request from the user terminal (S905). The authentication token is a token used to authenticate whether the user can use the application within the cloud service. At this time, the service console providing system authenticates the user's account information using the issued IDP token (S906). Then, the service console providing system can receive an access key setting API for the cloud service, which includes the access key information entered from the user terminal, the application to be used, and the credential validity period for the API call.
[0111] Thereafter, when the service console provision system transmits the access key information input from the user terminal to the first system (S907), the management module within the first system can log in to the authentication module installed within the authentication engine using the IDP token that has successfully been authenticated. Here, the first system (130) may be a KMS system.
[0112] Thereafter, the authentication module (132a) requests verification of the IDP token transmitted to the IDP module (120) (S908). Specifically, the authentication module (132a) can perform authentication using the IDP module (120) and logged-in authentication information. Here, the authentication method may adopt the JWT (JSON Web Token) authentication method, but is not limited thereto.
[0113] If the verification of the IDP token transmitted from the IDP module is successful, the IDP module transmits verification success information to the authentication module of the first system (S909). Thereafter, the access key information is stored in a key storage space within the authentication engine (S910). Along with the access key information, information on applications that can use the access key and information on the validity period of credentials for API calls may be stored. In addition, when the key storage space issues an authentication token containing the access key information to the management module, the management module transmits the authentication token to the service console providing system, and the service console providing system finally issues the authentication token to the user terminal (S911).
[0114] In this embodiment, the roles of the IAM module and the first system can be separated, such that the IAM module issues access keys and secret keys, while the first system transmits access key information, verifies the transmitted IDP token, and stores the access key information. Therefore, according to this embodiment, the load on each module or system can be effectively reduced.
[0115] Hereinafter, with reference to FIG. 11, a method for an application to provide a temporary key for credentials within a cloud service provision system after issuing an authentication token within the cloud service provision system will be described.
[0116] First, when the user terminal installs the authentication token issued to the application, the application requests the first system to issue a temporary key for credentials for calling an API serviced by the cloud service together with the issued authentication token (S912).
[0117] Thereafter, the first system performs authentication for the application using the authentication token included in the request for issuance of a temporary key (S913), and when the authentication is passed, issues a temporary key with a corresponding validity period according to the credential validity period information for API calls stored in the authentication token and transmits the temporary key to the application (S914).
[0118] Afterwards, the user terminal can use the services provided by the cloud service within the validity period after user authentication using the temporary key. According to this embodiment, by issuing a temporary key and allowing access to the cloud service by setting a validity period required for access to the cloud service, access keys and secret keys for the cloud service account do not need to be hard-coded in the source code or configuration files, thereby preventing the leakage of key information regarding the cloud service account. In addition, since only users and applications authenticated by the cloud service are issued and use temporary keys for authentication, the security of API calls can be enhanced.
[0119] FIG. 12 illustrates an exemplary computing system capable of implementing devices according to various embodiments of the present disclosure. Below, an exemplary computing system capable of implementing devices according to various embodiments of the present disclosure will be described with reference to FIG. 12.
[0120] FIG. 12 is a hardware configuration diagram showing a computing system (1000). As illustrated in FIG. 12, the computing system (1000) may include one or more processors (1100), a memory (1400) for loading a computer program executed by the processors (1100), a bus (1600), a communication interface (1200), and storage (1300) for storing the computer program (1500). However, FIG. 12 only illustrates components related to the embodiments of the present disclosure. Therefore, a person skilled in the art to which the present disclosure pertains may understand that other general components may be included in addition to the components illustrated in FIG. 12. The computing system (1000) of FIG. 12 may be the first cloud service providing system (10), the second cloud service providing system (20-1), or the third cloud service providing system (20-2) of FIG. 2.
[0121] The processor (1100) controls the overall operation of each component of the computing system (1000). The processor (1100) may include a central processing unit (CPU), a microprocessor unit (MPU), a microcontroller unit (MCU), a graphics processing unit (GPU), or any other type of processor well known in the art of the present disclosure. In addition, the processor (1100) may perform operations for at least one application or program for executing a method / operation according to embodiments of the present disclosure. The computing system (1000) may include one or more processors.
[0122] The memory (1400) stores various data, commands, and / or information. The memory (1400) can load one or more programs (1500) from the storage (1300) to execute methods / operations according to various embodiments of the present disclosure. The memory (1400) may be implemented as a volatile memory such as RAM, but the technical scope of the present disclosure is not limited thereto.
[0123] The bus (1600) provides communication between components of the computing system (1000). The bus (1600) may be implemented as various types of buses, such as an address bus, a data bus, and a control bus.
[0124] The communication interface (1200) supports wired and wireless Internet communication of the computing system (1000). Furthermore, the communication interface (1200) may support various communication methods other than Internet communication. To this end, the communication interface (1200) may be configured to include a communication module well known in the technical field of the present disclosure. In some cases, the communication interface (1200) may be omitted.
[0125] Storage (1300) can non-temporarily store one or more computer programs (1500) and various data, etc. Storage (1300) can be configured to include non-volatile memory such as flash memory, a hard disk, a removable disk, or any type of computer-readable recording medium well known in the technical field to which the present disclosure pertains.
[0126] The computer program (1500) may include one or more instructions that, when loaded into the memory (1400), cause the processor (1100) to perform methods / operations according to various embodiments of the present disclosure. That is, the processor (1100) may perform the methods / operations according to various embodiments of the present disclosure by executing the one or more instructions.
[0127] For example, the computer program (1500) may include instructions for performing an operation of transmitting data of a request page including a cloud service selection field for selecting one cloud service from a plurality of cloud service lists including a first cloud service and a second cloud service to a user terminal, an operation of receiving, from the user terminal, a request for issuance of a temporary key for credentials for calling an API serviced by the first cloud service, an operation of transmitting, in response to receiving the request for issuance of the temporary key, an operation of receiving, from the system of the first cloud service, key information for credentials for a first account issued to an organization operating the computing system, and an operation of transmitting, in response to the request for issuance of the temporary key, the key information for credentials to the user terminal.
[0128] Various embodiments of the present disclosure and effects according to the embodiments have been described with reference to FIGS. 1 through 12. The effects according to the technical concept of the present disclosure are not limited to the effects described above, and other effects not mentioned will be clearly understood by those skilled in the art from the description below.
[0129] The technical idea of the present disclosure described with reference to FIGS. 1 to 12 so far can be implemented as a computer-readable code on a computer-readable medium. The computer-readable recording medium can be, for example, a removable recording medium (CD, DVD, Blu-ray disc, USB storage device, removable hard disk) or a fixed recording medium (ROM, RAM, computer-attached hard disk). The computer program recorded on the computer-readable recording medium can be transmitted to another computing system via a network such as the Internet and installed in the other computing system, thereby being used in the other computing system.
[0130] Although all components constituting the embodiments of the present disclosure have been described as being combined or operating in combination as one, the technical concept of the present disclosure is not necessarily limited to such embodiments. That is, within the scope of the present disclosure, all components may be selectively combined and operated one or more times.
[0131] Although operations are depicted in the drawings in a particular order, this should not be understood to imply that the operations must be performed in the particular order depicted, or in any sequential order, or that all depicted operations must be performed to achieve the desired results. In certain circumstances, multitasking and parallel processing may be advantageous. Furthermore, the separation of the various components in the embodiments described above should not be understood to imply that such separation is absolutely necessary, and it should be understood that the program components and systems described may generally be integrated together into a single software product or packaged into multiple software products.
[0132] Although the embodiments of the present disclosure have been described with reference to the attached drawings, those skilled in the art will appreciate that the present disclosure can be implemented in other specific forms without changing the technical concepts or essential features thereof. Therefore, it should be understood that the embodiments described above are illustrative in all respects and not restrictive. The scope of protection of the present disclosure should be interpreted by the claims below, and all technical ideas within a scope equivalent thereto should be interpreted as being included within the scope of the technical ideas defined by the present disclosure.
Claims
1. In a method performed by a computing system, A step of transmitting data of a request page including a cloud service selection field for selecting one cloud service from a list of multiple cloud services including a second cloud service and a third cloud service to a user terminal; A step of receiving, from the user terminal, a request for issuance of a temporary key for credentials for calling an API (Application Programming Interface) serviced by the second cloud service selected in the cloud service selection field; In response to receiving a request for issuance of the temporary key, a step of transmitting an account issuance request signal to the system of the second cloud service; In response to the transmission of the account issuance request signal, a step of receiving, from the system of the second cloud service, key information for credentials for a first account issued to an institution operating the computing system; and Including a step of transmitting the credential key information to the user terminal in response to a request for issuance of the temporary key, Method of providing cloud service related credential services.
2. In paragraph 1, The above request page further includes a field for entering the validity period of the API call credentials, The step of sending the above account issuance request signal is: A step of transmitting an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the API call credentials, Method of providing cloud service related credential services.
3. In paragraph 2, The step of sending an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the above API call credentials is as follows: Including a step of transmitting a temporary account issuance request signal when the validity period entered through the request page corresponds to the validity period of a temporary account supported by the second cloud service. Method of providing cloud service related credential services.
4. In paragraph 1, The step of sending an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the above API call credentials is as follows: If the validity period entered through the request page does not correspond to the validity period of the temporary account supported by the second cloud service, a step of transmitting a permanent account issuance request signal is included. The step of transmitting the above key information is: When the validity period of the API call credentials expires, a step of sending an account deletion request signal to the system of the second cloud service is included. Method of providing cloud service related credential services.
5. In paragraph 1, The above request page further includes a field for entering the validity period of the API call credentials, The step of sending the above account issuance request signal is: comprising a step of transmitting a permanent account issuance request signal, The step of transmitting the above key information is: When the validity period of the API call credentials expires, a step of sending an account deletion request signal to the system of the second cloud service is included. Method of providing cloud service related credential services.
6. A method performed by a cloud service provision system including an ID Provider (IDP) module, an Identity and Access Management (IAM) module, and a first system, A step of receiving, from a user terminal, a request for issuing an authentication token for authentication to the cloud service, wherein the request for issuing an authentication token includes an access key issued by the IAM module and an IDP token and a temporary key issued by the IDP module, and information on the validity period of the temporary key; In response to receiving the authentication token issuance request, a step of transmitting a verification request for the IDP token to the IDP module; A step of receiving a verification result for the IDP token from the IDP module, and if the verification result is a verification success, the first system issues an authentication token and transmits the issued authentication token to the user terminal, and matching and storing the access key, the validity period information, and the authentication token included in the authentication token issuance request; The first system receives, from an application, a request for issuance of a temporary key for credentials for calling an API serviced by the cloud service, wherein the request for issuance of the temporary key includes the authentication token; and The first system performs authentication for the application using an authentication token included in the request for issuance of the temporary key, and when the authentication passes, issues a temporary key having a validity period according to the validity period information stored corresponding to the authentication token, and includes a step of transmitting the issued temporary key to the application. Method of providing cloud service related credential services.
7. One or more processors; and Contains memory that stores instructions, One or more of the above processors, By executing the above stored instructions, An action of transmitting data of a request page including a cloud service selection field for selecting one cloud service from a list of multiple cloud services including a second cloud service and a third cloud service to a user terminal; An action of receiving, from the user terminal, a request for issuance of a temporary key for credentials for calling an API (Application Programming Interface) serviced by the second cloud service selected in the cloud service selection field; In response to receiving a request for issuance of the temporary key, an action of transmitting an account issuance request signal to the system of the second cloud service; In response to the transmission of the above account issuance request signal, an operation of receiving, from the system of the first cloud service, key information for a credential for a first account issued to an institution operating the computing system; and In response to a request for issuance of the temporary key, an operation is performed to transmit the credential key information to the user terminal. Cloud service related credential service provision system.
8. In paragraph 7, The above request page further includes a field for entering the validity period of the API call credentials, The action of sending the above account issuance request signal is: Including an action of sending an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the API call credentials. Cloud service related credential service provision system.
9. In paragraph 8, The action of sending an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the above API call credentials is as follows: If the validity period entered through the request page corresponds to the validity period of a temporary account supported by the second cloud service, the operation of transmitting a temporary account issuance request signal is included. Cloud service related credential service provision system.
10. In paragraph 7, The action of sending an account issuance request signal requesting the issuance of a temporary account valid for a period corresponding to the validity period of the above API call credentials is as follows: If the validity period entered through the request page does not correspond to the validity period of the temporary account supported by the second cloud service, the operation of transmitting a permanent account issuance request signal is included. The action of transmitting the above key information is: When the validity period of the API call credentials expires, the operation of sending an account deletion request signal to the system of the second cloud service is included. Cloud service related credential service provision system.
11. In paragraph 7, The above request page further includes a field for entering the validity period of the API call credentials, The action of sending the above account issuance request signal is: Including an action for sending a permanent account issuance request signal, The action of transmitting the above key information is: When the validity period of the API call credentials expires, the operation of sending an account deletion request signal to the system of the second cloud service is included. Cloud service related credential service provision system.
Citation Information
Patent Citations
Method for establishing trust relationship between cloud services, and system
JP2012103931A
Device and method for recommending and integrating cloud service
KR101977536B1
A Simplified Secure Media based Authentication and Authorization for Cloud based Secure Services
KR1020160031937A
Disinfection robot system based on centralized remote control
KR1020240157808A
Method and apparatus for searching hidden IP address of malicious site using domain name system service
KR102684310B1
