Authorized interface docking method and device, equipment, storage medium and product
By using authorization link and rolling token to achieve dual authentication in the authorization interface docking, the problems of low efficiency and insufficient security of authorization interface docking in the existing technology are solved, and an efficient and secure authorization process is achieved.
Patent Information
- Application Number
- CN202411200200.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-29
- Publication Date
- 2024-12-10
AI Technical Summary
In the prior art, the docking efficiency of authorized interfaces is low, and the user needs to manually copy the credentials. The operation is complex and unsafe, and there is a risk of credential leakage.
When the target user and partner enable the service, call the user application authorization interface to obtain the authorization link, verify the identity information, generate the user authorization application, and use the scroll token to make the interface call to achieve dual-factor authentication and one-stop authorization, avoiding manual processing Copy the credentials.
It improves the efficiency of authorization interface docking, enhances security, avoids the leakage of credentials, and realizes an efficient authorization process without manually copying the credentials of both parties.
Smart Images
Figure CN119109596A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of data processing technology, and in particular to authorization interface docking methods, devices, equipment, storage media and products. Background Art
[0002] Authorization interface docking is applied to multiple systems, for example, system A and system B. After completing the authorization interface docking, data transmission between systems within the authorization scope is supported. Currently, user authorization is required for authorization interface docking, and the common operation of user authorization is to create credentials in system A and copy the credentials to system B, and use this credential in system B to access system A. However, the above method requires users to operate in system A and system B, and the operations in the systems are relatively complicated, and the credentials need to be copied manually. Therefore, the efficiency of authorization interface docking in the above method is low.
[0003] The above contents are only used to assist in understanding the technical solution of the present application and do not constitute an admission that the above contents are prior art. Summary of the invention
[0004] The main purpose of this application is to provide an authorization interface docking method, device, equipment, storage medium and product, aiming to solve the technical problem of low efficiency of authorization interface docking in the prior art.
[0005] To achieve the above purpose, the present application proposes an authorization interface docking method, the method comprising:
[0006] When the target user is determined and the service is started with the partner, the partner obtains the authorization link by calling the user application authorization interface;
[0007] After detecting that the target user opens the authorization page corresponding to the authorization link, verifying the identity information;
[0008] After the verification is passed and the target user's consent authorization information is received, a user authorization application is generated, and target application call docking information of the user authorization application is obtained;
[0009] The partner calls the interface based on the target application call docking information and rolling token.
[0010] In one embodiment, after detecting that the target user opens the authorization page corresponding to the authorization link, the step of verifying the identity information includes:
[0011] After detecting that the target user opens the authorization page corresponding to the authorization link, obtaining the identity information of the target user and the identity information of the enterprise;
[0012] When verifying that the target user is an enterprise administrator according to the identity information of the target user, assisting the target user in performing real-name authentication according to the real-name authentication prompt information;
[0013] Assist the enterprise to carry out advanced authentication according to the enterprise authentication prompt information.
[0014] In one embodiment, after the step of obtaining the identity information of the target user and the identity information of the enterprise, the step further includes:
[0015] When it is verified based on the identity information of the target user that the target user is not an enterprise administrator, a prompt message that an administrator operation is required is generated and displayed;
[0016] Determine the contact information of the enterprise administrator and obtain the identification code of the authorization page;
[0017] The identification code of the authorization page is sent to the terminal corresponding to the enterprise administrator according to the contact information.
[0018] In one embodiment, after the verification is passed and the consent authorization information of the target user is received, the step of generating a user authorization application and obtaining the target application call docking information of the user authorization application includes:
[0019] After the verification is passed and the consent authorization information of the target user is received, the standard enterprise management platform will review the consent authorization information;
[0020] After the review is passed, a user authorization application is generated based on the authorization application template;
[0021] Open the permission of the user-authorized application to call the interface, and obtain the target calling information of the user-authorized application;
[0022] The target call information is encrypted to obtain target application call docking information, and the target application call docking information is fed back to the partner by the standard enterprise management platform;
[0023] When the partner fails to obtain the target application call docking information, the standard enterprise management platform is triggered to feed back the target application call docking information again by calling a designated interface.
[0024] In one embodiment, after the step of obtaining the target application call docking information of the user authorized application, the method further includes:
[0025] Determine the current authorized interface based on the target application call docking information;
[0026] Counting the number of currently authorized interfaces;
[0027] When the quantity does not meet the preset requirement, determine the number of newly opened authorization interfaces according to the quantity and the preset requirement;
[0028] Open authorization interfaces corresponding to the number of the newly opened authorization interfaces on the user authorization application.
[0029] In one embodiment, the step of calling the interface by the partner according to the target application calling the docking information and the rolling token includes:
[0030] Generate a rolling token according to a preset token generation rule, and set the validity period of the rolling token;
[0031] Encrypt the set rolling token;
[0032] Push the encrypted rolling token to the partner in a preset way;
[0033] The partner decrypts the encrypted rolling token and adjusts the original calling strategy based on the target parameters to obtain a target calling strategy;
[0034] Based on the target calling strategy, an interface call is performed according to the target application calling docking information and the decrypted rolling token.
[0035] In addition, to achieve the above purpose, the present application also proposes an authorization interface docking device, the authorization interface docking device comprising:
[0036] The acquisition module is used for obtaining the authorization link by calling the user application authorization interface when the target user is determined to start the service with the partner;
[0037] A verification module, used to verify the identity information after detecting that the target user opens the authorization page corresponding to the authorization link;
[0038] A generation module, used to generate a user authorization application after verification and receipt of the target user's consent authorization information, and obtain the target application call docking information of the user authorization application;
[0039] The calling module is used for the partner to call the interface according to the target application calling docking information and the rolling token.
[0040] In addition, to achieve the above-mentioned purpose, the present application also proposes an authorization interface docking device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, and the computer program is configured to implement the steps of the authorization interface docking method described above.
[0041] In addition, to achieve the above-mentioned purpose, the present application also proposes a storage medium, which is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by the processor, the steps of the authorization interface docking method described above are implemented.
[0042] In addition, to achieve the above-mentioned purpose, the present application also provides a computer program product, which includes a computer program, and when the computer program is executed by a processor, the steps of the authorization interface docking method described above are implemented.
[0043] One or more technical solutions proposed in the present application have at least the following technical effects: when determining the target user and the partner to start the service, the partner obtains the authorization link by calling the user application authorization interface; after detecting that the target user opens the authorization page corresponding to the authorization link, the identity information is verified; after the verification is passed and the target user's consent authorization information is received, a user authorization application is generated, and the target application call docking information of the user authorization application is obtained; the partner makes an interface call based on the target application call docking information and the rolling token; through the above method, after the target user opens the authorization page, the identity information of the target user and the enterprise is double authenticated to ensure the security of the authorization, and then the user authorization application is generated by using the authorization application template, and then the interface call is made in combination with the rolling token, so as to achieve one-stop authorization, effectively improve the efficiency of the authorization interface docking, and do not need to manually copy the credentials of both parties to avoid the leakage of credentials. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] The accompanying drawings herein are incorporated in and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the description, are used to explain the principles of the present application.
[0045] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, for ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0046] Figure 1 A flowchart of the first embodiment of the method for connecting the authorization interface of this application is provided;
[0047] Figure 2 A flowchart of the second embodiment of the authorization interface connection method of this application is provided;
[0048] Figure 3 A brief flowchart of the authorization interface docking method provided in Example 2 of the present application;
[0049] Figure 4 This is a schematic diagram of the module structure of the authorization interface docking device according to an embodiment of the present application;
[0050] Figure 5 Schematic diagram of the device structure of the hardware operating environment involved in the authorization interface docking method in the embodiment of the present application.
[0051] The purpose, features and advantages of this application will be further described in conjunction with the embodiments and with reference to the accompanying drawings. DETAILED DESCRIPTION
[0052] It should be noted that the execution subject of this embodiment can be a computing service device with data processing, network communication and program running functions, such as a tablet computer, a personal computer, a mobile phone, etc., or an electronic device capable of realizing the above functions, an authorization interface docking system, etc. The following takes the authorization interface docking as an example to illustrate this embodiment and the following embodiments.
[0053] Based on this, the present application embodiment provides an authorization interface docking method, referring to Figure 1 , Figure 1 This is a flow chart of the first embodiment of the authorization interface docking method of this application.
[0054] In this embodiment, the authorization interface docking method includes steps S10 to S40:
[0055] Step S10: When it is determined that the target user and the partner start the service, the partner obtains the authorization link by calling the user application authorization interface.
[0056] It should be noted that the authorization interface docking system of this embodiment includes a partner, a standard enterprise management platform and a user terminal, wherein the standard business management platform can be Xinfutong, and the partner's Software as a Service (SaaS) platform is a platform that provides application services through the Internet, without the need to install and maintain applications locally.
[0057] It should be understood that when the target user is determined to start the service with the partner, it indicates that the authorization interface needs to be connected at this time. The authorization link refers to the link to generate the authorization page. The authorization link is obtained by calling the user application authorization interface. In the user application authorization interface, the social credit unified code is transmitted as the unique key, and the authorization link for each tenant is different. In addition, for the partner, it is necessary to complete registration, authentication, and create an interface application in the standard enterprise management platform, obtain the calling interface certificate of the partner application, and check the configuration content of the authorization application template with the standard enterprise management platform. The configuration content includes but is not limited to the target user's authorized application name, the interface to be used, events, and the Internet IP export whitelist where the server is located.
[0058] Step S20, after detecting that the target user opens the authorization page corresponding to the authorization link, verify the identity information.
[0059] It is understandable that after clicking the authorization link, the authorization page corresponding to the authorization link is opened, that is, the partner guides the target user to open the authorization page, and the authorization link can be pushed via SMS to achieve a one-stop user experience. For the target user, after opening the authorization page, he needs to log in, and then verify the identity information from both the user and the enterprise dimensions to ensure the dual identities of the enterprise and the user.
[0060] Step S30, after the verification is passed and the target user's consent authorization information is received, a user authorization application is generated, and target application call docking information of the user authorization application is obtained.
[0061] It should be understood that the consent authorization information can be the information of consent authorization after checking the interface and event as needed. When the target user authorizes, the authorization page will provide a list of interfaces and events that can be selected. The target user can check as needed and agree to the authorization. In order to prevent the target user from under-authorizing, the partner will explain to the customer in advance the interfaces and events that need to be authorized for the relevant business. If the partner needs to display the authorization status in real time, it can actively query the authorization result. In addition, the authorization status includes but is not limited to initiated, administrator rejected, under review, passed and rejected, etc. When the authorization status reaches the final state, it can no longer be circulated. The standard enterprise management platform will notify the partner through an event. The final state includes but is not limited to administrator rejected, passed and rejected, etc. Only when the authorization status is passed can the user authorization application be generated and the interface empowerment be completed.
[0062] It can be understood that after the dual identity information verification is passed, it is determined in real time whether the target user's consent and authorization information is received. If so, the user authorization application is generated using the authorization application template. The target authorized application refers to the application authorized by the target user. The target application call docking information refers to the relevant docking information for calling the user-authorized application. The target application call docking information includes but is not limited to application keys, calling interfaces, etc.
[0063] Further, step S30 includes: after the verification is passed and the consent authorization information of the target user is received, the standard enterprise management platform reviews the consent authorization information; after the review is passed, a user authorization application is generated based on the authorization application template; the permission of the calling interface of the user authorization application is opened, and the target calling information of the user authorization application is obtained; the target calling information is encrypted to obtain the target application calling docking information, and the standard enterprise management platform feeds back the target application calling docking information to the partner; if the partner fails to obtain the target application calling docking information, the standard enterprise management platform is triggered by calling the specified interface to feed back the target application calling docking information again.
[0064] It is understandable that consent to authorization information also includes signing a service agreement. After verification and receipt of the target user's consent to authorization information, the standard enterprise management platform will review the relevant content in the consent to authorization information in the background. After the review is passed, the authorization will officially take effect, that is, the user authorization application and the permission to open the calling interface will be generated. In order to effectively improve the security of data transmission, the target call information needs to be encrypted into target application call docking information, and then the standard enterprise management platform will push the target application call docking information to the partner. For the partner, after obtaining the target application call docking information, it is necessary to save the target application call docking information so that it can be used to call the standard enterprise management platform interface for subsequent services to the target user. On the other hand, when the target application call docking information is not obtained or the processing fails, the standard enterprise management platform is triggered to feedback the target application call docking information again by calling the specified interface in a compensation manner.
[0065] Furthermore, after the step of obtaining the target application call docking information of the user authorized application, it also includes: determining the current authorization interface based on the target application call docking information; counting the number of the current authorization interfaces; when the number does not meet the preset requirements, determining the number of newly opened authorization interfaces based on the number and the preset requirements; and opening the authorization interface corresponding to the number of newly opened authorization interfaces on the user authorized application.
[0066] It should be understood that when it is determined that the current number of authorized interfaces does not meet the preset requirements, it indicates that the current application scenario has been authorized once, but the authorized interfaces are insufficient and more interfaces need to be authorized. In addition, the interface can also be replaced by an event, but since no new application will be created after the authorization is approved, the authorization interface corresponding to the number of newly opened authorization interfaces will be opened directly on the user authorization application, or an authorization event. In other words, each enterprise will only have one user authorization application, but can have multiple authorization applications. When an authorization does not reach the final state, a new authorization application will not be initiated, and the target user will enter the ongoing authorization result display page.
[0067] Step S40: The partner calls the interface according to the target application calling docking information and the rolling token.
[0068] It can be understood that the rolling token can be a rolling token. For the partner, after receiving the target application call information, the interface call is made in combination with the rolling token, thereby ensuring the security of user data. In addition, this embodiment will create a partner application and a user application, and then call the corresponding interfaces respectively to ensure data isolation.
[0069] Furthermore, step S40 includes: generating a rolling token according to a preset token generation rule, and setting the validity period of the rolling token; encrypting the set rolling token; pushing the encrypted rolling token to the partner in a preset manner; the partner decrypting the encrypted rolling token, and adjusting the original calling strategy based on the target parameters to obtain a target calling strategy; based on the target calling strategy, making an interface call according to the target application calling docking information and the decrypted rolling token.
[0070] It should be understood that in this embodiment, the user-authorized application needs to carry a rolling token to call the interface, but there is no such requirement for events. The preset token generation rule refers to the rule for generating a rolling token, for example, it is generated once every ten minutes, and then the validity period of the rolling token is set. For example, the validity period is two hours. The preset method can be a data push method. In order to ensure the security of transmitting the rolling token, the rolling token with a set validity period needs to be encrypted. For the partner, after decrypting the rolling token, the original calling strategy needs to be adjusted based on the target parameter, which can be the CSCTOKEN parameter. The specific adjustment method is to assemble the CSCTOKEN parameter in the queryParam string in the original calling strategy. At this time, when calling the interface, the partner needs to use the valid rolling token carried by the user-authorized application identity.
[0071] It should be noted that the user authorization application given to partners is subject to validity period restrictions, with the default validity period being 365 days. When it is detected that the target user's authorization validity period is ≤30 days, a list of users whose authorization is about to expire will be pushed to the partner through an event. If the corresponding users need to continue to be served, it is recommended to guide the user to renew the authorization. Renewal requires the user to log in to the standard enterprise management platform for manual operation.
[0072] In this embodiment, when it is determined that the target user and the partner start the service, the partner obtains the authorization link by calling the user application authorization interface; after detecting that the target user opens the authorization page corresponding to the authorization link, the identity information is verified; after the verification is passed and the target user's consent authorization information is received, a user authorization application is generated, and the target application call docking information of the user authorization application is obtained; the partner makes an interface call based on the target application call docking information and the rolling token; through the above method, after the target user opens the authorization page, the identity information of the target user and the enterprise is double-authenticated to ensure the security of the authorization, and then the user authorization application is generated using the authorization application template, and then the interface call is made in combination with the rolling token, thereby achieving one-stop authorization and effectively improving the efficiency of the authorization interface docking, without the need to manually copy the credentials of both parties to avoid the leakage of credentials.
[0073] Based on the first embodiment of the present application, in the second embodiment of the present application, the same or similar contents as those in the above-mentioned embodiment 1 can be referred to the above introduction, and will not be repeated in the following. Figure 2 , step S20 includes steps S201 to S203:
[0074] Step S201, after detecting that the target user opens the authorization page corresponding to the authorization link, obtaining the identity information of the target user and the identity information of the enterprise.
[0075] It should be noted that after the target user opens the authorization page, he / she needs to log in first. This login needs to ensure the dual identities of the enterprise and the user. At this time, the identity information of the target user and the identity information of the enterprise can be obtained.
[0076] Furthermore, after step S201, it also includes: when it is verified that the target user is not an enterprise administrator based on the identity information of the target user, generating and displaying a prompt message requiring administrator operation; determining the contact information of the enterprise administrator and obtaining the identification code of the authorization page; and sending the identification code of the authorization page to the terminal corresponding to the enterprise administrator based on the contact information.
[0077] It should be noted that when it is verified that the target user is not an enterprise administrator, the target user will not be allowed to continue the authorization operation. The prompt information that administrator operation is required refers to the information prompting the enterprise that an enterprise administrator must perform the authorization operation. The contact information can be a mobile phone number, and the identification code of the authorization page can be a QR code. At this time, the identification code of the authorization page is sent to the terminal corresponding to the enterprise administrator according to the contact information, so that the enterprise administrator can perform subsequent authorization operations.
[0078] Step S202, when verifying that the target user is an enterprise administrator according to the identity information of the target user, assisting the target user in performing real-name authentication according to real-name authentication prompt information.
[0079] It is understandable that for user identity, it is necessary to verify whether the target user is an enterprise administrator and perform real-name authentication. The real-name authentication prompt information refers to the prompt information that assists the target user in performing real-name authentication, for example, prompting the user to perform face recognition, specify action recognition, etc.
[0080] Step S203, assisting the enterprise to perform advanced authentication according to the enterprise authentication prompt information.
[0081] It should be understood that the enterprise authentication prompt information refers to the prompt information to assist enterprises in advanced authentication. At this time, you can use the enterprise authentication system of China Merchants Bank. Specifically, for the corporate identity, a fixed enterprise will be opened based on the unified social credit code logged in by the partner, and the enterprise is required to complete advanced authentication, that is, after online verification and manual authentication by the branch, to ensure that the enterprise information is normal and other enterprises cannot be opened for authorization on the partner.
[0082] It should be noted that if the target user does not have an account registered on the standard enterprise management platform, the login account registration will be automatically completed when logging in. If the user has not registered an enterprise on the standard enterprise management platform, the target user needs to visit the official website of the standard enterprise management platform to log in and register the enterprise. Note: The authorization page does not provide an enterprise registration entrance, so the target user needs to complete the enterprise registration by himself. The target user has the right to perform authorization operations only when the target user successfully logs in and is identified as an enterprise administrator recorded in the standard enterprise management platform.
[0083] This embodiment obtains the identity information of the target user and the identity information of the enterprise after detecting that the target user opens the authorization page corresponding to the authorization link; when verifying that the target user is an enterprise administrator based on the identity information of the target user, assisting the target user in performing real-name authentication based on the real-name authentication prompt information; and assisting the enterprise in performing advanced authentication based on the enterprise authentication prompt information; through the above method, after detecting that the target user opens the authorization page, the target user and enterprise information are double-verified according to the identity information, and when verifying that the target user is an enterprise administrator, the target user is assisted in performing real-name authentication, and the enterprise is assisted in performing advanced authentication, thereby ensuring the legitimacy of the target user and the enterprise, and thereby improving the security of the authorization operation.
[0084] For example, to help understand the implementation process of the authorization interface docking method obtained by combining this embodiment with the above-mentioned embodiment 1, please refer to Figure 3 , Figure 3A brief flowchart of an authorization interface docking method is provided, specifically:
[0085] Take the partner, standard enterprise management platform and user terminal as an example to explain, specifically: when the target user is determined to start the service with the partner, the partner obtains the authorization link by calling the user application authorization interface. At this time, the partner will guide the target user to open the authorization page corresponding to the authorization link, that is, complete the access to the authorization page, and then the target user will check the authorization content after logging in. At this time, the standard enterprise management platform will review the consent authorization information in the background. After the review is passed, a user authorization application is generated based on the authorization application template, the user authorization application's calling interface permission is opened, and the target application call docking information is pushed to the partner. At this time, if the partner has not obtained the target application call docking information, the partner will trigger the standard enterprise management platform to feedback the target application call docking information again by calling the specified interface in a compensation manner, and then continue to use the rolling token to make interface calls.
[0086] It should be noted that the above examples are only used to understand the present application and do not constitute a limitation on the authorization interface docking method of the present application. More simple transformations based on this technical concept are all within the protection scope of the present application.
[0087] This application also provides an authorization interface docking device, please refer to Figure 4 , the authorization interface docking device comprises:
[0088] The acquisition module 10 is used for obtaining the authorization link by the partner by calling the user application authorization interface when it is determined that the target user and the partner start the service.
[0089] The verification module 20 is used to verify the identity information after detecting that the target user opens the authorization page corresponding to the authorization link.
[0090] The generating module 30 is used to generate a user authorized application and obtain the target application call docking information of the user authorized application after the verification is passed and the consent authorization information of the target user is received.
[0091] The calling module 40 is used for the partner to call the interface according to the target application calling docking information and the rolling token.
[0092] In this embodiment, when it is determined that the target user and the partner start the service, the partner obtains the authorization link by calling the user application authorization interface; after detecting that the target user opens the authorization page corresponding to the authorization link, the identity information is verified; after the verification is passed and the target user's consent authorization information is received, a user authorization application is generated, and the target application call docking information of the user authorization application is obtained; the partner makes an interface call based on the target application call docking information and the rolling token; through the above method, after the target user opens the authorization page, the identity information of the target user and the enterprise is double-authenticated to ensure the security of the authorization, and then the user authorization application is generated using the authorization application template, and then the interface call is made in combination with the rolling token, thereby achieving one-stop authorization and effectively improving the efficiency of the authorization interface docking, without the need to manually copy the credentials of both parties to avoid the leakage of credentials.
[0093] The authorization interface docking device provided by the present application adopts the authorization interface docking method in the above embodiment, which can solve the technical problem of low efficiency of authorization interface docking in the prior art. Compared with the prior art, the beneficial effects of the authorization interface docking device provided by the present application are the same as the beneficial effects of the authorization interface docking method provided by the above embodiment, and other technical features in the authorization interface docking device are the same as the features disclosed in the above embodiment method, which will not be repeated here.
[0094] In one embodiment, the verification module 20 is also used to obtain the identity information of the target user and the identity information of the enterprise after detecting that the target user opens the authorization page corresponding to the authorization link; when verifying that the target user is an enterprise administrator based on the identity information of the target user, assisting the target user in performing real-name authentication according to the real-name authentication prompt information; and assisting the enterprise in performing advanced authentication according to the enterprise authentication prompt information.
[0095] In one embodiment, the verification module 20 is also used to generate and display administrator operation prompt information when the target user is verified not to be an enterprise administrator based on the identity information of the target user; determine the contact information of the enterprise administrator and obtain the identification code of the authorization page; and send the identification code of the authorization page to the terminal corresponding to the enterprise administrator based on the contact information.
[0096] In one embodiment, the generation module 30 is also used to review the consent authorization information by the standard enterprise management platform after the verification is passed and the consent authorization information of the target user is received; after the review is passed, generate a user authorization application based on the authorization application template; open the permission of the calling interface of the user authorization application, and obtain the target calling information of the user authorization application; encrypt the target calling information to obtain the target application calling docking information, and the standard enterprise management platform feeds back the target application calling docking information to the partner; if the partner fails to obtain the target application calling docking information, trigger the standard enterprise management platform to feed back the target application calling docking information again by calling the specified interface.
[0097] In one embodiment, the generation module 30 is also used to determine the current authorization interface based on the target application calling docking information; count the number of the current authorization interfaces; when the number does not meet the preset requirements, determine the number of newly opened authorization interfaces based on the number and the preset requirements; and open the authorization interface corresponding to the number of newly opened authorization interfaces on the user authorization application.
[0098] In one embodiment, the calling module 40 is also used to generate a rolling token according to a preset token generation rule, and set the validity period of the rolling token; encrypt the set rolling token; push the encrypted rolling token to the partner in a preset manner; the partner decrypts the encrypted rolling token and adjusts the original calling strategy based on the target parameters to obtain a target calling strategy; based on the target calling strategy, an interface call is made according to the target application calling docking information and the decrypted rolling token.
[0099] The present application provides an authorization interface docking device, which includes: at least one processor; and 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 so that the at least one processor can execute the authorization interface docking method in the above-mentioned embodiment one.
[0100] Reference below Figure 5, which shows a schematic diagram of the structure of an authorization interface docking device suitable for implementing the embodiment of the present application. The authorization interface docking device in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (Personal Digital Assistants), PADs (Portable Application Descriptions), PMPs (Portable Media Players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. Figure 5 The authorization interface docking device shown is merely an example and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
[0101] like Figure 5 As shown, the authorization interface docking device may include a processing device 1001 (e.g., a central processing unit, a graphics processor, etc.), which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM: Read Only Memory) 1002 or a program loaded from a storage device 1003 to a random access memory (RAM: Random Access Memory) 1004. In RAM1004, various programs and data required for the operation of the authorization interface docking device are also stored. The processing device 1001, ROM1002, and RAM1004 are connected to each other through a bus 1005. An input / output (I / O) interface 1006 is also connected to the bus. Generally, the following systems can be connected to the I / O interface 1006: an input device 1007 including, for example, a touch screen, a touch pad, a keyboard, a mouse, an image sensor, a microphone, an accelerometer, a gyroscope, etc.; an output device 1008 including, for example, a liquid crystal display (LCD: Liquid Crystal Display), a speaker, a vibrator, etc.; a storage device 1003 including, for example, a magnetic tape, a hard disk, etc.; and a communication device 1009. The communication device 1009 can allow the authorization interface docking device to communicate wirelessly or wired with other devices to exchange data. Although the figure shows an authorization interface docking device with various systems, it should be understood that it is not required to implement or have all the systems shown. More or fewer systems can be implemented or provided instead.
[0102] In particular, according to the embodiments disclosed in the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, the embodiments disclosed in the present application include a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through a communication device, or installed from a storage device 1003, or installed from a ROM 1002. When the computer program is executed by the processing device 1001, the above-mentioned functions defined in the method of the embodiment disclosed in the present application are executed.
[0103] The authorization interface docking device provided by the present application adopts the authorization interface docking method in the above embodiment, which can solve the technical problem of low efficiency of authorization interface docking in the prior art. Compared with the prior art, the beneficial effects of the authorization interface docking device provided by the present application are the same as the beneficial effects of the authorization interface docking method provided by the above embodiment, and other technical features in the authorization interface docking device are the same as the features disclosed in the method of the previous embodiment, which will not be repeated here.
[0104] It should be understood that the various parts disclosed in this application can be implemented by hardware, software, firmware or a combination thereof. In the description of the above embodiments, specific features, structures, materials or characteristics can be combined in any one or more embodiments or examples in a suitable manner.
[0105] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.
[0106] The present application provides a computer-readable storage medium having computer-readable program instructions (ie, computer programs) stored thereon, and the computer-readable program instructions are used to execute the authorization interface docking method in the above-mentioned embodiment.
[0107] The computer-readable storage medium provided in the present application may be, for example, a USB flash drive, but is not limited to electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, systems or devices, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM: Erasable Programmable Read Only Memory or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM: CD-Read Only Memory), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this embodiment, the computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, system or device. The program code contained on the computer-readable storage medium may be transmitted using any appropriate medium, including but not limited to: wires, optical cables, RF (Radio Frequency), etc., or any suitable combination of the above.
[0108] The computer-readable storage medium may be included in the authorization interface docking device; or may exist independently without being assembled into the authorization interface docking device.
[0109] Computer program code for performing the operations of the present application may be written in one or more programming languages or a combination thereof, including object-oriented programming languages such as Java, Smalltalk, C++, and conventional procedural programming languages such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).
[0110] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.
[0111] The modules involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of the module does not constitute a limitation on the unit itself in some cases.
[0112] The readable storage medium provided by the present application is a computer-readable storage medium, which stores computer-readable program instructions (i.e., computer programs) for executing the above-mentioned authorization interface docking method, and can solve the technical problem of low efficiency of authorization interface docking in the prior art. Compared with the prior art, the beneficial effects of the computer-readable storage medium provided by the present application are the same as the beneficial effects of the authorization interface docking method provided by the above-mentioned embodiment, and will not be repeated here.
[0113] The present application also provides a computer program product, including a computer program, which implements the steps of the above-mentioned authorization interface docking method when executed by a processor.
[0114] The computer program product provided by this application can solve the technical problem of low efficiency of authorization interface docking in the prior art. Compared with the prior art, the beneficial effects of the computer program product provided by this application are the same as the beneficial effects of the authorization interface docking method provided by the above embodiment, which will not be repeated here.
[0115] The above descriptions are only some embodiments of the present application, and are not intended to limit the patent scope of the present application. All equivalent structural changes made using the contents of the present application specification and drawings under the technical concept of the present application, or direct / indirect applications in other related technical fields are included in the patent protection scope of the present application.
Claims
1. An authorization interface docking method, characterized in that: The method comprises: When the target user is determined and the service is started with the partner, the partner obtains the authorization link by calling the user application authorization interface; After detecting that the target user opens the authorization page corresponding to the authorization link, verifying the identity information; After the verification is passed and the target user's consent authorization information is received, a user authorization application is generated, and target application call docking information of the user authorization application is obtained; The partner calls the interface based on the target application call docking information and rolling token.
2. The method according to claim 1, characterized in that The step of verifying the identity information after detecting that the target user opens the authorization page corresponding to the authorization link includes: After detecting that the target user opens the authorization page corresponding to the authorization link, obtaining the identity information of the target user and the identity information of the enterprise; When verifying that the target user is an enterprise administrator according to the identity information of the target user, assisting the target user in performing real-name authentication according to the real-name authentication prompt information; Assist the enterprise to carry out advanced authentication according to the enterprise authentication prompt information.
3. The method according to claim 2, characterized in that After the step of obtaining the identity information of the target user and the identity information of the enterprise, the method further includes: When it is verified based on the identity information of the target user that the target user is not an enterprise administrator, a prompt message that an administrator operation is required is generated and displayed; Determine the contact information of the enterprise administrator and obtain the identification code of the authorization page; The identification code of the authorization page is sent to the terminal corresponding to the enterprise administrator according to the contact information.
4. The method according to claim 1, characterized in that The step of generating a user-authorized application after the verification is passed and the target user's consent authorization information is received, and obtaining the target application call docking information of the user-authorized application includes: After the verification is passed and the consent authorization information of the target user is received, the standard enterprise management platform will review the consent authorization information; After the review is passed, a user authorization application is generated based on the authorization application template; Open the permission of the user-authorized application to call the interface, and obtain the target calling information of the user-authorized application; The target call information is encrypted to obtain target application call docking information, and the target application call docking information is fed back to the partner by the standard enterprise management platform; When the partner fails to obtain the target application call docking information, the standard enterprise management platform is triggered to feed back the target application call docking information again by calling a designated interface.
5. The method according to claim 1, characterized in that After the step of obtaining the target application call docking information of the user authorized application, the method further includes: Determine the current authorized interface based on the target application call docking information; Counting the number of currently authorized interfaces; When the quantity does not meet the preset requirement, determine the number of newly opened authorization interfaces according to the quantity and the preset requirement; Open authorization interfaces corresponding to the number of the newly opened authorization interfaces on the user authorization application.
6. The method according to any one of claims 1 to 5, characterized in that The step of the partner calling the interface according to the target application calling the docking information and the rolling token includes: Generate a rolling token according to a preset token generation rule, and set the validity period of the rolling token; Encrypt the set rolling token; Push the encrypted rolling token to the partner in a preset way; The partner decrypts the encrypted rolling token and adjusts the original calling strategy based on the target parameters to obtain a target calling strategy; Based on the target calling strategy, an interface call is performed according to the target application calling docking information and the decrypted rolling token.
7. An authorization interface docking device, characterized in that: The device comprises: The acquisition module is used for obtaining the authorization link by calling the user application authorization interface when the target user is determined to start the service with the partner; A verification module, used to verify the identity information after detecting that the target user opens the authorization page corresponding to the authorization link; A generation module, used to generate a user authorization application after verification and receipt of the target user's consent authorization information, and obtain the target application call docking information of the user authorization application; The calling module is used for the partner to call the interface according to the target application calling docking information and the rolling token.
8. An authorization interface docking device, characterized in that: The device comprises: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is configured to implement the steps of the authorization interface docking method according to any one of claims 1 to 6.
9. A storage medium, characterized in that: The storage medium is a computer-readable storage medium, and a computer program is stored on the storage medium. When the computer program is executed by a processor, the steps of the authorization interface docking method according to any one of claims 1 to 6 are implemented.
10. A computer program product, characterized in that The computer program product comprises a computer program, and when the computer program is executed by a processor, the steps of the authorization interface docking method according to any one of claims 1 to 6 are implemented.