RPA robot authorization method, device and system and storage medium

Abstract

The invention discloses an RPA robot authorization method, device and system and a storage medium, and relates to the technical field of computers. The method is applied to an RPA robot, and specifically comprises the following steps: acquiring authorization certificate information sent by a scheduler; the authorization certificate information is determined based on a first public key, a first private key, a second public key and preset configuration information; the first public key and the first private key are key pairs of the server; acquiring a user identifier and a first public key of the RPA robot; based on the user identifier and a first public key, performing authorization verification processing on the authorization certificate information to obtain a verification processing result; and outputting a result of the verification processing to the scheduler, so that the scheduler performs marking processing on the state of the certificate of authorization based on the result of the verification processing.

Description

Technical Field

[0001] The present application relates to the field of computer technology, specifically to technical fields such as big data technology and data collection technology, and in particular to a method, device, system, and storage medium for RPA robot authorization. Background Art

[0002] In application scenarios with strict requirements on external network access rights, Robotic Process Automation (RPA) robots are generally deployed locally. Specifically, certificates can be issued to each RPA robot. The verification of the certificate content is usually linked to the hardware. When the robot is running, the legitimacy of the certificate can be verified based on the hardware.

[0003] However, when the hardware changes, the certificate also needs to be replaced. Moreover, when virtual technology is used, the hardware information running the RPA robot changes frequently, resulting in a huge workload for replacing the certificate. Summary of the invention

[0004] The present application provides a method, device, system, and storage medium for RPA robot authorization, which can solve the problem of poor authentication efficiency of RPA robots. The technical solution is as follows:

[0005] In a first aspect, a method for authorizing an RPA robot is provided, which is applied to an RPA robot, and the method includes:

[0006] Obtaining the authorization certificate information sent by the scheduler; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and preset configuration information; the first public key and the first private key are the key pair of the server;

[0007] Obtaining a user ID and a first public key of the RPA robot;

[0008] Based on the user identifier and the first public key, performing authorization verification processing on the authorization certificate information to obtain a verification processing result;

[0009] The result of the verification process is output to the scheduler, so that the scheduler marks the status of the authorization certificate based on the result of the verification process.

[0010] In a possible implementation manner, obtaining the authorization certificate information sent by the scheduler includes:

[0011] Sending a request to obtain the authorization certificate information to the scheduler, so that the scheduler performs a request verification process on the RPA robot based on the acquisition request, and in response to a result of the verification process satisfying a preset first verification condition, sending the authorization certificate information to the RPA robot;

[0012] Obtain the authorization certificate information sent by the scheduler.

[0013] In a possible implementation, performing authorization verification processing on the authorization certificate information based on the user identifier and the first public key to obtain a verification processing result includes:

[0014] Based on the preset second verification condition, the user identifier and the first public key, performing authorization verification processing on the authorization certificate information;

[0015] In response to the user identification and the first public key satisfying a preset second verification condition, determining that a result of the verification process is verification passed;

[0016] In response to the user identification and the first public key not satisfying a preset second verification condition, it is determined that the result of the verification process is verification failure.

[0017] In a possible implementation manner, enabling the scheduler to mark the status of the authorization certificate based on the result of the verification process includes:

[0018] so that the scheduler marks the status of the authorization certificate as allocated if the result of the verification process is that the verification is passed;

[0019] So that the scheduler marks the status of the authorization certificate as unallocated when the result of the verification process is that the verification fails.

[0020] In a possible implementation, the authorization certificate information includes a signature, a user identifier, a certificate code, a start time, and an end time.

[0021] In a second aspect, a device for authorizing an RPA robot is provided, which is applied to an RPA robot, and the device includes:

[0022] A first acquisition unit is used to acquire the authorization certificate information sent by the scheduler; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and preset configuration information; the first public key and the first private key are a key pair of the server;

[0023] A second acquisition unit is used to acquire a user identifier and a first public key of the RPA robot;

[0024] An authorization verification unit, configured to perform authorization verification processing on the authorization certificate information based on the user identifier and the first public key to obtain a verification processing result;

[0025] The result output unit is used to output the result of the verification process to the scheduler, so that the scheduler marks the status of the authorization certificate based on the result of the verification process.

[0026] In a third aspect, a system for authorizing an RPA robot is provided, wherein the system for authorizing an RPA robot includes an RPA robot and a scheduler; wherein:

[0027] The RPA robot is used to perform the method of the above aspects and any possible implementation method;

[0028] The scheduler is used to mark the status of the authorization certificate based on the result of the verification process.

[0029] In a fourth aspect, a computer-readable storage medium is provided, wherein at least one instruction is stored in the storage medium, and the at least one instruction is loaded and executed by a processor to implement the method of the above-mentioned aspect and any possible implementation manner.

[0030] According to a fifth aspect, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the above-mentioned aspects and any possible implementation method.

[0031] The beneficial effects of the technical solution provided by this application include at least:

[0032] It can be seen from the above technical solution that the embodiment of the present application can obtain the authorization certificate information sent by the scheduler through the RPA robot, and obtain the user identification and the first public key of the RPA robot; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and the preset configuration information; the first public key and the first private key are the key pair of the server, and then the authorization certificate information can be authorized and verified based on the user identification and the first public key to obtain the result of the verification process, so that the result of the verification process can be output to the scheduler, so that the scheduler can mark the status of the authorization certificate based on the result of the verification process. Since the RPA robot can be based on the built-in user identification and the first public key, through interactive verification with the scheduler, the verification of the authorization certificate can be realized, which can avoid the binding of the certificate with the hardware information, and there is no need to replace the certificate due to changes in the hardware information. While improving the adaptability of the virtualized resources authorized and authenticated by the RPA robot, the reliability of the RPA robot authorization and authentication can also be guaranteed.

[0033] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0034] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0035] Figure 1 This is a flowchart of a method for RPA robot authorization provided by an embodiment of the present application;

[0036] Figure 2 It is a schematic diagram of an interaction process of an application scenario of a method for RPA robot authorization provided by another embodiment of the present application;

[0037] Figure 3 It is a schematic diagram of the architecture of an RPA robot authorization device provided by another embodiment of the present application;

[0038] Figure 4 It is a block diagram of an electronic device used to implement the RPA robot authorization method of an embodiment of the present application. DETAILED DESCRIPTION

[0039] The following is a description of exemplary embodiments of the present application in conjunction with the accompanying drawings, including various details of the embodiments of the present application to facilitate understanding, which should be considered as merely exemplary. Therefore, it should be recognized by those of ordinary skill in the art that various changes and modifications can be made to the embodiments described herein without departing from the scope and spirit of the present application. Similarly, for the sake of clarity and conciseness, the description of well-known functions and structures is omitted in the following description.

[0040] Obviously, the described embodiments are only part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.

[0041] It should be noted that the terminal devices involved in the embodiments of the present application may include but are not limited to mobile phones, personal digital assistants (PDAs), wireless handheld devices, tablet computers and other smart devices; display devices may include but are not limited to personal computers, televisions and other devices with display functions.

[0042] In addition, the term "and / or" in this article is only a description of the association relationship between the associated objects, indicating that there can be three relationships. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this article generally indicates that the associated objects before and after are in an "or" relationship.

[0043] Please refer to Figure 1 , which shows a flow chart of a method for RPA robot authorization provided by an embodiment of the present application. The method for RPA robot authorization can be applied to RPA robots, and specifically may include:

[0044] Step 101, obtain the authorization certificate information sent by the scheduler; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and preset configuration information; the first public key and the first private key are the key pair of the server.

[0045] Step 102: Obtain the user ID and first public key of the RPA robot.

[0046] Step 103: Based on the user identifier and the first public key, authorization verification processing is performed on the authorization certificate information to obtain a verification processing result.

[0047] Step 104: Output the verification result to the scheduler, so that the scheduler marks the status of the authorization certificate based on the verification result.

[0048] At this point, the authorization process for the RPA robot can be completed.

[0049] It should be noted that the first private key may be a private key pre-configured by the server. The server may be a company providing RPA robot services, etc. Here, the first public key may be a public key pre-configured by the server. The first private key and the first public key may be used as a root certificate.

[0050] It should be noted that the preset configuration information may include a user identifier, a certificate code, a start time, and an end time, etc.

[0051] It should be noted that the user identifier and the first public key of the RPA robot may be pre-configured inside the RPA robot.

[0052] It should be noted that the server may be provided with a first public key and a first private key. The client may be provided with a second public key and a second private key. The client may send the second public key and the second private key to the server to generate a ciphertext of the authorization certificate corresponding to the client. Each client has multiple corresponding authorization certificates.

[0053] It should be noted that the scheduler of each client can decode the ciphertext of the received multiple authorization certificates based on the second private key, and store the obtained plaintext storage of the authorization certificates.

[0054] In this way, the RPA robot can obtain the authorization certificate information sent by the scheduler, and obtain the user identification and the first public key of the RPA robot; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and the preset configuration information; the first public key and the first private key are the key pair of the server, and then the authorization certificate information can be authorized and verified based on the user identification and the first public key to obtain the result of the verification process, so that the result of the verification process can be output to the scheduler, so that the scheduler can mark the status of the authorization certificate based on the result of the verification process. Since the RPA robot can interact with the scheduler based on the built-in user identification and the first public key to verify the authorization certificate, the binding of the certificate to the hardware information can be avoided, and there is no need to replace the certificate due to changes in hardware information. While improving the adaptability of the virtualized resources authorized and authenticated by the RPA robot, the reliability of the RPA robot authorization and authentication can be guaranteed.

[0055] Optionally, in a possible implementation of this embodiment, in step 101, a request for obtaining the authorization certificate information is sent to the scheduler, so that the scheduler performs request verification processing on the RPA robot based on the acquisition request, and in response to the result of the verification processing satisfying a preset first verification condition, the authorization certificate information is sent to the RPA robot, and the authorization certificate information sent by the scheduler can be obtained.

[0056] In this implementation, the number of authorization certificates in the scheduler may be multiple. The authorization certificate information may be obtained by decoding the authorization certificate provided by the server based on the second private key. The number of authorization certificates provided by the server may be multiple. The number of authorization certificates provided by the server may be determined according to actual business needs.

[0057] Here, the acquisition request may include a user identifier and a first public key. The preset first verification condition may include that the user identifier and the first public key match the authorization certificate information, and the scheduler has an idle authorization certificate.

[0058] In a specific implementation process of this implementation method, in response to the user identifier and the first public key matching the authorization certificate information, and the scheduler having an idle authorization certificate, the authorization certificate information is sent to the RPA robot, and then the RPA robot can obtain the authorization certificate information sent by the scheduler.

[0059] Optionally, in a possible implementation of this embodiment, in step 102, first, authorization verification processing can be performed on the authorization certificate information based on the preset second verification condition, the user identifier and the first public key. Secondly, in response to the user identifier and the first public key satisfying the preset second verification condition, the result of the verification processing is determined to be verification passed, or in response to the user identifier and the first public key not satisfying the preset second verification condition, the result of the verification processing is determined to be verification failed.

[0060] In this implementation, the preset second verification condition may include passing the signature verification of the authorization certificate information based on the user identifier and the first public key, and the system time of the RPA robot being the valid time.

[0061] In this implementation, if the verification result is a successful verification, it can indicate that the RPA robot is authorized successfully. If the verification result is a failed verification, it can indicate that the RPA robot is not authorized successfully.

[0062] In a specific implementation process of this implementation, in step 103, when the result of the verification process is that the verification is passed, the scheduler marks the status of the authorization certificate as allocated.

[0063] Alternatively, when the result of the verification process is that the verification fails, the scheduler marks the status of the authorization certificate as unallocated.

[0064] In another specific implementation process of this implementation method, after step 103, when the scheduler receives the RPA robot destruction information, the scheduler can recycle the authorization certificate of the RPA robot when the RPA robot is destroyed, and can mark the status of the authorization certificate as unallocated again.

[0065] It is understandable that when the RPA robot is not executing business, the scheduler can revoke the authorization certificate and destroy the RPA robot to release resources.

[0066] It should be noted that the specific implementation process provided in this implementation can be combined with the various specific implementation processes provided in the aforementioned implementation to implement the RPA robot authorization method of this embodiment. For a detailed description, please refer to the relevant content in the aforementioned implementation, which will not be repeated here.

[0067] Optionally, in a possible implementation of this embodiment, the authorization certificate information includes a signature, a user identifier, a certificate code, a start time, and an end time.

[0068] In a specific implementation process of this implementation method, for any authorization certificate information, the user identification, certificate code, start time, and end time can be signed using the first private key to obtain the signature.

[0069] In this implementation, the user identifier may be a customer number, and the customer may use the RPA robot.

[0070] Here, the validity period of the authorization certificate may be obtained based on the start time and the end time.

[0071] It should be noted that the specific implementation process provided in this implementation can be combined with the various specific implementation processes provided in the aforementioned implementation to implement the RPA robot authorization method of this embodiment. For a detailed description, please refer to the relevant content in the aforementioned implementation, which will not be repeated here.

[0072] In order to better illustrate the RPA robot authorization method in this application, the RPA robot authorization method is now described in detail in combination with specific application scenarios.

[0073] Figure 2 is a schematic diagram of an interaction process of an application scenario of a method for RPA robot authorization provided by another embodiment of the present application, such as Figure 2 In this embodiment, the application scenario includes an RPA robot and a scheduler.

[0074] Step 201: Send a request to obtain authorization certificate information.

[0075] In this embodiment, the authorization certificate information is determined based on the first public key, the first private key, the second public key, and preset configuration information. The first public key and the first private key are a key pair of the server.

[0076] In this embodiment, the authorization certificate information includes a signature, a user identifier, a certificate code, a start time, and an end time.

[0077] In this embodiment, the scheduler may pre-configure multiple authorization certificates corresponding to the second public key. The authorization certificate in the scheduler may be an authorization certificate that has been decoded based on the second private key.

[0078] It is understandable that the server may be provided with a first public key and a first private key. The client may be provided with a second public key and a second private key. The client may send the second public key and the second private key to the server.

[0079] Step 202: Perform request verification processing on the RPA robot based on the acquisition request, and in response to the result of the verification processing satisfying the preset first verification condition, feedback the authorization certificate information.

[0080] Step 203: Obtain authorization certificate information, the user ID and the first public key of the RPA robot.

[0081] In this embodiment, the RPA robot may be pre-configured with a user identifier and a first public key.

[0082] Step 204: Based on the user identifier and the first public key, authorization verification processing is performed on the authorization certificate information to obtain a verification processing result.

[0083] In this embodiment, the RPA robot performs authorization verification on the authorization certificate information based on the preset second verification condition, user identification and first public key. In response to the user identification and the first public key satisfying the preset second verification condition, the result of the verification process is determined to be verification passed. In response to the user identification and the first public key not satisfying the preset second verification condition, the result of the verification process is determined to be verification failed.

[0084] Here, the preset second verification condition may include that the authorization certificate information is verified based on the user identifier and the first public key, and the system time of the RPA robot is valid.

[0085] Furthermore, the system time of the RPA robot can be obtained, the user identifier and the first public key can be verified with the authorization certificate information, and the system time can be matched with the start time and end time in the authorization certificate information. When the authorization certificate information is verified and the system time of the RPA robot is valid, the result of the verification process can be determined as verification passed; when the authorization certificate information is not verified and / or the system time of the RPA robot is valid, the result of the verification process can be determined as verification failed.

[0086] Step 205: Output the result of the verification process.

[0087] Step 206: Based on the result of the verification process, mark the status of the authorization certificate.

[0088] In this embodiment, the scheduler may mark the status of the authorization certificate as allocated if the result of the verification process is that the verification is passed.

[0089] Alternatively, the scheduler may mark the status of the authorization certificate as unassigned if the result of the verification process is that the verification fails.

[0090] Step 207: In response to destroying the RPA robot, the authorization certificate is recycled.

[0091] In this embodiment, illustratively, first, the company on the server side can pre-set the public key Pu1 and private key Pr1 of the RPA robot as the root certificate. The client of the RPA robot can also pre-set the public key Pu2 and private key Pr2. When the client of the RPA robot needs an RPA authorization certificate, it can send its public key Pu2 to the company on the server side of the RPA robot. The company on the server side generates an RPA authorization certificate for the client of the RPA robot. The content of the authorization certificate can be an encrypted ciphertext based on Pu2, and the content of the authorization certificate ciphertext includes signature + certificate code + user ID + start time + end time. Among them, the signature content can be the result of signing the certificate code + user ID + start time + end time using Pr1.

[0092] Here, Pu1 may be the first public key, Pr1 may be the first private key, Pu2 may be the second public key, Pr2 may be the second private key, and the user identifier may be the customer number.

[0093] Secondly, after the RPA robot customer obtains the authorization certificate, it imports it into the client's scheduler, decodes the authorization certificate based on the private key Pr2, and obtains the plain text content of the authorization certificate, that is, the certificate code + user ID + start time + end time, and can store the plain text content of the authorization certificate in the scheduler. Here, the number of authorization certificates can be multiple.

[0094] Again, the RPA robot has a built-in user ID and the server's public key Pu1. When the RPA robot is started, it can send a request to the scheduler to obtain an authorization certificate. The scheduler can send an unassigned authorization certificate to the RPA robot. After receiving the authorization certificate, the RPA robot can verify the legitimacy of the authorization certificate based on the public key Pu1 and the user ID, that is, perform public key signature verification, and verify the validity period of the RPA robot. After the verification is completed, the verification result is fed back to the scheduler, and the scheduler can change the status of the verified authorization certificate to assigned. At this point, other business communications can be carried out. In addition, when the RPA robot is destroyed, the scheduler will reclaim the certificate corresponding to the RPA robot.

[0095] In this way, by adopting the solution in this embodiment, the RPA robot can complete the complete verification of the certificate and adapt to virtualized resources through the built-in client number and the public key of the server based on the interactive processing with the scheduler, thereby realizing that the certificate is not bound to the hardware information, avoiding the problem of replacing the certificate when the hardware information changes.

[0096] In addition, by adopting the solution in this embodiment, the authorization certificate does not have to be fixedly bound to a certain RPA robot. The certificate needs to be applied for only when the RPA robot executes business. Otherwise, the authorization certificate can be withdrawn, the RPA robot can be destroyed, and resources can be released, thereby improving the utilization rate of hardware resources.

[0097] In addition, using the solution in this embodiment, the authorization certificate itself is encrypted and requires the user's private key to decrypt and use. At the same time, the user ID is also solidified in the RPA robot, which can achieve non-interoperability of certificates and prevent users of different RPA robots from interoperating.

[0098] It should be noted that, for the above-mentioned embodiments, for the sake of simplicity, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described order of actions, because according to the present application, certain steps can be performed in other orders or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.

[0099] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.

[0100] Figure 3 A structural block diagram of an RPA robot authorization device provided by an embodiment of the present application is shown as follows: Figure 3 As shown. The RPA robot authorization device 300 of this embodiment is applied to the RPA robot and may include a first acquisition unit 301, a second acquisition unit 302, an authorization verification unit 303 and a result output unit 304. Among them, the first acquisition unit 301 is used to obtain the authorization certificate information sent by the scheduler; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and the preset configuration information; the first public key and the first private key are the key pair of the server; the second acquisition unit 302 is used to obtain the user identifier and the first public key of the RPA robot; the authorization verification unit 303 is used to perform authorization verification processing on the authorization certificate information based on the user identifier and the first public key to obtain the result of the verification processing; the result output unit 304 is used to output the result of the verification processing to the scheduler, so that the scheduler marks the status of the authorization certificate based on the result of the verification processing.

[0101] Optionally, in a possible implementation of this embodiment, the first acquisition unit 301 is used to send a request to obtain the authorization certificate information to the scheduler, so that the scheduler performs request verification processing on the RPA robot based on the acquisition request, and in response to the result of the verification processing satisfying a preset first verification condition, sends the authorization certificate information to the RPA robot; obtain the authorization certificate information sent by the scheduler.

[0102] Optionally, in a possible implementation of this embodiment, the authorization verification unit 303 is used to perform authorization verification processing on the authorization certificate information based on a preset second verification condition, the user identifier and the first public key; in response to the user identifier and the first public key satisfying the preset second verification condition, determining that the result of the verification processing is verification passed; in response to the user identifier and the first public key not satisfying the preset second verification condition, determining that the result of the verification processing is verification failed.

[0103] Optionally, in a possible implementation of this embodiment, the result output unit 304 is used to enable the scheduler to mark the status of the authorization certificate as allocated when the result of the verification process is that the verification is passed; and to enable the scheduler to mark the status of the authorization certificate as unallocated when the result of the verification process is that the verification is failed.

[0104] Optionally, in a possible implementation of this embodiment, the authorization certificate information includes a signature, a user identifier, a certificate code, a start time, and an end time.

[0105] In this embodiment, the authorization certificate information sent by the scheduler can be obtained by the first acquisition unit; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and the preset configuration information; the first public key and the first private key are the key pair of the server, the second acquisition unit obtains the user identification and the first public key of the RPA robot, and the authorization verification unit performs authorization verification processing on the authorization certificate information based on the user identification and the first public key to obtain the result of the verification processing, so that the result output unit can output the result of the verification processing to the scheduler, so that the scheduler can mark the status of the authorization certificate based on the result of the verification processing. Since the RPA robot can interact with the scheduler based on the built-in user identification and the first public key to verify the authorization certificate, the binding of the certificate to the hardware information can be avoided, and there is no need to replace the certificate due to changes in hardware information. While improving the adaptability of the virtualized resources authorized and authenticated by the RPA robot, the reliability of the RPA robot authorization and authentication can also be guaranteed.

[0106] One embodiment of the technical solution of the present application further provides a system for RPA robot authorization, which may include an RPA robot and a scheduler. The RPA robot may be used to execute the RPA robot authorization method in the aforementioned method embodiment. The scheduler may be used to mark the status of the authorization certificate based on the result of the verification process.

[0107] Optionally, in a possible implementation of this embodiment, the scheduler may be used to store at least one authorization certificate.

[0108] Optionally, in a possible implementation of this embodiment, the RPA robot may be used to send a request to obtain the authorization certificate information to the scheduler. The scheduler may be used to perform request verification processing on the RPA robot based on the acquisition request, and in response to the result of the verification processing satisfying a preset first verification condition, send the authorization certificate information to the RPA robot. The RPA robot may be used to obtain the authorization certificate information sent by the scheduler.

[0109] Optionally, in a possible implementation of this embodiment, the RPA robot can be used to perform authorization verification processing on the authorization certificate information based on a preset second verification condition, the user identifier and the first public key. In response to the user identifier and the first public key satisfying the preset second verification condition, the result of the verification processing is determined to be verification passed; in response to the user identifier and the first public key not satisfying the preset second verification condition, the result of the verification processing is determined to be verification failed.

[0110] In a specific implementation process of this implementation, the scheduler may be used to mark the status of the authorization certificate as allocated if the result of the verification process is that the verification is passed.

[0111] Alternatively, the scheduler may be configured to mark the status of the authorization certificate as unallocated when the result of the verification process is that the verification fails.

[0112] Optionally, in a possible implementation of this embodiment, the scheduler may be used to recycle the authorization certificate when the RPA robot is destroyed.

[0113] In the technical solution of this application, the user personal information involved, such as the collection, storage, use, processing, transmission, provision and disclosure of user images and attribute data, etc., complies with the provisions of relevant laws and regulations and does not violate public order and good morals.

[0114] According to an embodiment of the present application, the present application also provides an electronic device, a readable storage medium and a computer program product.

[0115] Figure 4 A schematic block diagram of an example electronic device 400 that can be used to implement an embodiment of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0116] like Figure 4 As shown, the electronic device 400 includes a computing unit 401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 402 or a computer program loaded from a storage unit 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the electronic device 400 can also be stored. The computing unit 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0117] Multiple components in the electronic device 400 are connected to the I / O interface 405, including: an input unit 406, such as a keyboard, a mouse, etc.; an output unit 407, such as various types of displays, speakers, etc.; a storage unit 408, such as a disk, an optical disk, etc.; and a communication unit 409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 409 allows the electronic device 400 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0118] The computing unit 401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 401 performs the various methods and processes described above, such as the method of RPA robot authorization. For example, in some embodiments, the method of RPA robot authorization may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 400 via the ROM 402 and / or the communication unit 409. When the computer program is loaded into the RAM 403 and executed by the computing unit 401, one or more steps of the method of RPA robot authorization described above may be performed. Alternatively, in other embodiments, the computing unit 401 may be configured to perform the method of RPA robot authorization in any other appropriate manner (e.g., by means of firmware).

[0119] Various implementations of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various implementations can include: being implemented in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0120] The program code for implementing the method of the present application can be written in any combination of one or more programming languages. These program codes can be provided to a processor or controller of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the program code, when executed by the processor or controller, implements the functions / operations specified in the flow chart and / or block diagram. The program code can be executed entirely on the machine, partially on the machine, partially on the machine and partially on a remote machine as a stand-alone software package, or entirely on a remote machine or server.

[0121] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0122] To provide interaction with a user, the systems and techniques described herein can be implemented on a computer having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0123] The systems and techniques described herein may be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or a web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), and the Internet.

[0124] A computer system may include a client and a server. The client and the server are generally remote from each other and usually interact through a communication network. The relationship of client and server is generated by computer programs running on respective computers and having a client-server relationship with each other. The server may be a cloud server, a server of a distributed system, or a server combined with a blockchain.

[0125] It should be understood that the various forms of processes shown above can be used to reorder, add or delete steps. For example, the steps recorded in this disclosure can be executed in parallel, sequentially or in different orders, as long as the desired results of the technical solution disclosed in this application can be achieved, and this document is not limited here.

[0126] The above specific implementations do not constitute a limitation on the protection scope of this application. It should be understood by those skilled in the art that various modifications, combinations, sub-combinations and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions and improvements made within the spirit and principles of this application should be included in the protection scope of this application.

Claims

1. A method for authorizing an RPA robot, characterized in that: Applied to an RPA robot, the method includes: Obtaining the authorization certificate information sent by the scheduler; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and preset configuration information; the first public key and the first private key are the key pair of the server; Obtaining a user ID and a first public key of the RPA robot; Based on the user identifier and the first public key, performing authorization verification processing on the authorization certificate information to obtain a verification processing result; The result of the verification process is output to the scheduler, so that the scheduler marks the status of the authorization certificate based on the result of the verification process.

2. The method according to claim 1, characterized in that The obtaining of the authorization certificate information sent by the scheduler includes: Sending a request to obtain the authorization certificate information to the scheduler, so that the scheduler performs a request verification process on the RPA robot based on the acquisition request, and in response to a result of the verification process satisfying a preset first verification condition, sending the authorization certificate information to the RPA robot; Obtain the authorization certificate information sent by the scheduler.

3. The method according to claim 1, characterized in that The performing authorization verification processing on the authorization certificate information based on the user identifier and the first public key to obtain a verification processing result includes: Based on the preset second verification condition, the user identifier and the first public key, performing authorization verification processing on the authorization certificate information; In response to the user identification and the first public key satisfying a preset second verification condition, determining that a result of the verification process is verification passed; In response to the user identification and the first public key not satisfying a preset second verification condition, it is determined that the result of the verification process is verification failure.

4. The method according to claim 3, characterized in that The step of causing the scheduler to mark the status of the authorization certificate based on the result of the verification process includes: so that the scheduler marks the status of the authorization certificate as allocated if the result of the verification process is that the verification is passed; So that the scheduler marks the status of the authorization certificate as unallocated when the result of the verification process is that the verification fails.

5. The method according to any one of claims 1 to 4, characterized in that The authorization certificate information includes a signature, a user identifier, a certificate code, a start time, and an end time.

6. A device for RPA robot authorization, characterized in that: Applied to an RPA robot, the device includes: A first acquisition unit is used to acquire the authorization certificate information sent by the scheduler; the authorization certificate information is determined based on the first public key, the first private key, the second public key, and preset configuration information; the first public key and the first private key are a key pair of the server; A second acquisition unit is used to acquire a user identifier and a first public key of the RPA robot; An authorization verification unit, configured to perform authorization verification processing on the authorization certificate information based on the user identifier and the first public key to obtain a verification processing result; The result output unit is used to output the result of the verification process to the scheduler, so that the scheduler marks the status of the authorization certificate based on the result of the verification process.

7. A system for RPA robot authorization, characterized in that: The RPA robot authorization system includes an RPA robot and a scheduler; wherein, The RPA robot is used to perform the method according to any one of claims 1 to 5; The scheduler is used to mark the status of the authorization certificate based on the result of the verification process.

8. An electronic device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1 to 5.

9. A non-transitory computer-readable storage medium storing computer instructions, characterized in that: The computer instructions are used to cause the computer to execute the method according to any one of claims 1-5.

10. A computer program product, characterized in that The invention comprises a computer program which, when executed by a processor, implements the method according to any one of claims 1 to 5.

Images