CN116886763A - Butt joint method, service butt joint method and system of universal three-party access platform - Google Patents
Butt joint method, service butt joint method and system of universal three-party access platform Download PDFInfo
- Publication number
- CN116886763A CN116886763A CN202311152580.1A CN202311152580A CN116886763A CN 116886763 A CN116886763 A CN 116886763A CN 202311152580 A CN202311152580 A CN 202311152580A CN 116886763 A CN116886763 A CN 116886763A
- Authority
- CN
- China
- Prior art keywords
- platform
- party
- access
- tenant
- universal
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 53
- 210000001503 joint Anatomy 0.000 title claims abstract description 22
- 238000003032 molecular docking Methods 0.000 claims abstract description 52
- 238000013475 authorization Methods 0.000 claims description 25
- 230000006978 adaptation Effects 0.000 claims description 15
- 238000003860 storage Methods 0.000 claims description 10
- 238000004590 computer program Methods 0.000 claims description 9
- 238000010276 construction Methods 0.000 claims description 3
- 230000008901 benefit Effects 0.000 abstract description 4
- 238000012545 processing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 5
- 230000007547 defect Effects 0.000 description 3
- 238000010586 diagram Methods 0.000 description 3
- 238000012937 correction Methods 0.000 description 2
- 238000013461 design Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 238000007726 management method Methods 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000007781 pre-processing Methods 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000009960 carding Methods 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000008878 coupling Effects 0.000 description 1
- 238000010168 coupling process Methods 0.000 description 1
- 238000005859 coupling reaction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 238000005538 encapsulation Methods 0.000 description 1
- 238000009776 industrial production Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000035515 penetration Effects 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/50—Network services
- H04L67/53—Network services using third party service providers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
Abstract
The invention belongs to the technical field of software development, and provides a docking method, a service docking method and a service docking system of a universal three-party access platform. The butt joint method comprises the following steps: extracting first elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the first elements; wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; building tenant access configuration of a general three-party access platform based on second elements carried by each tenant; wherein the second element comprises: access name, access status, account key, target platform; and realizing the butt joint of the tenant and a target third party platform in the general three party access platform based on the access configuration. The service docking method is realized based on the docking method, and the system is also built based on the docking method. The invention has the advantages of simple access and high access efficiency when the multi-tenant multi-third party platform is in butt joint.
Description
Technical Field
The invention relates to the technical field of software development, in particular to a docking method, a service docking method and a service docking system of a universal three-party access platform.
Background
With the gradual penetration of computer technology into people's daily life and industrial production, software systems or software platforms with various specific functions are also gradually perfected.
In order to facilitate development and application of software platforms with various specific functions, a high-integration-level large-scale three-party platform capable of covering various fields is gradually becoming a basic platform for various software development, for example, a large-scale PaaS platform is a large-scale cloud platform for providing various software development, testing and management application programs.
However, the inventor finds that the high-integration large-scale three-party platform still has the following technical defects in practical application: with more and more software platforms (i.e. third party platforms) are docked, the system design and business logic writing of the high-integration large-scale three-party platform are more complex. When the tenant is in butt joint with the software platform, the high-integration large-scale three-party platform is still carried out in a traditional code writing mode, so that the problems of complex butt joint and low butt joint efficiency of the multi-tenant and multi-software platform are caused, and the three-party platform cannot be effectively applied to an actual scene.
Disclosure of Invention
The invention aims to provide a butt joint method, a business butt joint method and a system of a general three-party access platform, so as to solve the technical problem that the efficiency of the existing high-integration-level large-scale three-party platform is low when multi-tenant multi-third-party platform butt joint is carried out.
In order to achieve the above purpose, the present invention proposes the following technical scheme:
in a first aspect, the present technical solution provides a docking method of a universal three-party access platform, including:
extracting first elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the first elements;
wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; the platform name is used for identifying a corresponding third party platform by a tenant in the general three-party access platform, the platform address is used for identifying an API prefix of the corresponding third party platform by the general three-party access platform, the platform identifier is used for identifying the same type of third party platform by the general three-party access platform, and the platform grouping is used for the general three-party access platform to distinguish mutually exclusive same type of third party platforms;
building tenant access configuration of the universal three-party access platform based on second elements carried by each tenant;
wherein the second element comprises: access name, access status, account key and target platform; the access name is used for tenant identification of the universal three-party access platform, the access state is used for controlling access opening or access closing of tenants by the universal three-party access platform, the account key is used for authorizing authentication of the tenants by the universal three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the universal three-party access platform;
and realizing the butt joint of the tenant and a target third party platform in the general three party access platform based on the access configuration.
Further, the first element carried by each third party platform is extracted, so that each third party platform is preconfigured to the universal three party access platform based on the first element; further comprises:
extracting third elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the third elements;
wherein the third element comprises: global access and authentication information; and the global access is used for the universal three-party access platform to open corresponding third-party platforms for all tenants, and the authentication information is used for the universal three-party access platform to perform access authentication on the third-party platforms which are pre-opened for all tenants.
In a second aspect, the present technical solution provides a service docking method of a universal three-party access platform, where the service docking method includes:
acquiring a service request of a tenant; the service request is used for requesting to acquire any service corresponding to any accessed third party platform by the tenant;
calling the access configuration of the tenant based on a route distinguishing component and a third party platform corresponding to the service to traverse an adaptation processor of the third party platform so as to acquire a service interface corresponding to the service;
when judging that the tenant does not acquire authentication of a third party platform corresponding to the service based on the RPC interceptor, calling a third party authorization component to authorize and authenticate the tenant based on the pre-configuration information of the third party platform and the access configuration information of the tenant;
and returning the service content corresponding to the service request to the tenant.
Further, the routing discrimination component invokes the access configuration of the tenant and the third party platform corresponding to the service to traverse the adaptation processor of the third party platform to obtain the service interface corresponding to the service; comprising the following steps:
storing the access configuration of the tenant and a third party platform corresponding to the service to directly call when the tenant reinitiates any service request corresponding to the third party platform.
Further, after obtaining the service request of the tenant, the method includes:
and when the third party platform corresponding to the service request is pre-configured to the universal three-party access platform based on the third element, skipping the step of calling the access configuration of the tenant based on the route distinguishing component and traversing the adaptation processor of the third party platform by the third party platform corresponding to the service so as to acquire the service interface corresponding to the service.
Further, when the RPC-based interceptor judges that the tenant does not acquire authentication of a third party platform corresponding to the service, a third party authorization component is called to perform authorization authentication on the tenant based on pre-configuration information of the third party platform and access configuration information of the tenant; comprising the following steps:
and acquiring the effective duration of the third party platform authorization of the account corresponding to the authorization authentication, and storing the authorization token acquired by the account key according to the effective duration.
In a third aspect, the present technical solution provides a docking system of a universal three-party access platform, including:
the first configuration module is used for extracting first elements carried by each third party platform so as to pre-configure each third party platform to the universal three party access platform based on the first elements;
wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; the platform name is used for identifying a corresponding third party platform by a tenant in the general three-party access platform, the platform address is used for identifying an API prefix of the corresponding third party platform by the general three-party access platform, the platform identifier is used for identifying the same type of third party platform by the general three-party access platform, and the platform grouping is used for the general three-party access platform to distinguish mutually exclusive same type of third party platforms;
the interface construction module is used for constructing tenant access configuration of the general three-party access platform based on second elements carried by each tenant;
wherein the second element comprises: access name, access status, account key, target platform; the access name is used for tenant identification of the universal three-party access platform, the access state is used for controlling access opening or access closing of tenants by the universal three-party access platform, the account key is used for authorizing authentication of the tenants by the universal three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the universal three-party access platform;
and the docking module is used for realizing docking of the tenant and a target third party platform in the general three party access platform based on the access configuration.
Further, the method comprises the steps of:
the second configuration module is used for extracting third elements carried by each third party platform so as to pre-configure each third party platform to the universal three party access platform based on the third elements;
wherein the third element comprises: global access and authentication information; and the global access is used for the universal three-party access platform to open corresponding third-party platforms for all tenants, and the authentication information is used for the universal three-party access platform to perform access authentication on the third-party platforms which are pre-opened for all tenants.
In a fourth aspect, the present disclosure provides an electronic device comprising at least one processor coupled to a memory, the memory having stored therein a computer program configured to perform the method when executed by the processor.
In a fifth aspect, the present disclosure provides a computer readable storage medium having a computer program stored thereon, the computer program being configured to perform the method.
The beneficial effects are that:
according to the technical scheme, the technical scheme of the invention provides a docking method of the universal three-party access platform, so that the technical defect that the universal three-party access platform in the prior art has low docking efficiency when a third-party platform is accessed, particularly a tenant, is overcome.
The butt joint method comprises the following steps: firstly, extracting a first element carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the first element; wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; the platform name is used for the general three-party access platform to identify the corresponding third-party platform, the platform address is used for the general three-party access platform to confirm the API prefix of the corresponding third-party platform, the platform identification is used for the general three-party access platform to confirm the same type of third-party platform, and the platform grouping is used for the general three-party access platform to distinguish mutually exclusive same type of third-party platforms. Secondly, establishing tenant access configuration of the universal three-party access platform based on second elements carried by each tenant; wherein the second element comprises: access name, access status, account key and target platform; the access name is used for tenant identification of the universal three-party access platform, the access state is used for controlling access opening or access closing of tenants by the universal three-party access platform, the account key is used for authorizing authentication of the tenants by the universal three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the universal three-party access platform. And finally, realizing the butt joint of the tenant and a target third party platform in the general three party access platform based on the access configuration.
Therefore, the technical scheme mainly comprises the general three-party access platform, the abstract processing is adopted for the access of the third-party platform and the access of the tenant, and the unified encapsulation of the third-party platform and the tenant during the access is completed; the first element corresponding to the first element is extracted from the third party platform abstract as the information required by the first element to be accessed to the general three party access platform, and the second element of the tenant is used as the information required by the second element to be accessed to the specific third party platform in the tenant configuration abstract. And furthermore, when the tenant is accessed to the corresponding third party platform based on the general three-party access platform, the quick docking of the tenant and the third party platform can be realized based on the corresponding element acquisition matching.
It should be understood that all combinations of the foregoing concepts, as well as additional concepts described in more detail below, may be considered a part of the inventive subject matter of the present disclosure as long as such concepts are not mutually inconsistent.
The foregoing and other aspects, embodiments, and features of the present teachings will be more fully understood from the following description, taken together with the accompanying drawings. Other additional aspects of the invention, such as features and/or advantages of the exemplary embodiments, will be apparent from the description which follows, or may be learned by practice of the embodiments according to the teachings of the invention.
Drawings
The drawings are not intended to be drawn to scale. In the drawings, each identical or nearly identical component that is illustrated in various figures may be represented by a like numeral. For purposes of clarity, not every component may be labeled in every drawing. Embodiments of various aspects of the invention will now be described, by way of example, with reference to the accompanying drawings, in which:
fig. 1 is a flowchart of a docking method of a universal three-party access platform according to the present embodiment;
FIG. 2 is a flow chart of a third party platform global access to a general-purpose third party access platform in the present embodiment;
fig. 3 is a flowchart of a service docking method of the universal three-party access platform according to the present embodiment;
fig. 4 is a flowchart of service request preprocessing in the present embodiment;
FIG. 5 is a flowchart for improving the service docking efficiency according to the present embodiment;
FIG. 6 is another flow chart for improving the service docking efficiency according to the present embodiment;
fig. 7 is a schematic structural diagram of a docking system of the universal three-party access platform according to the present embodiment;
fig. 8 is a schematic structural diagram of an electronic device according to the present embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present invention more clear, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. It will be apparent that the described embodiments are some, but not all, embodiments of the invention. All other embodiments, which can be made by a person skilled in the art without creative efforts, based on the described embodiments of the present invention fall within the protection scope of the present invention. Unless defined otherwise, technical or scientific terms used herein should be given the ordinary meaning as understood by one of ordinary skill in the art to which this invention belongs.
The terms "first," "second," and the like in the description and in the claims, are not used for any order, quantity, or importance, but are used for distinguishing between different elements. Also, unless the context clearly indicates otherwise, singular forms "a," "an," or "the" and similar terms do not denote a limitation of quantity, but rather denote the presence of at least one. The terms "comprises," "comprising," or the like are intended to cover a feature, integer, step, operation, element, and/or component recited as being present in the element or article that "comprises" or "comprising" does not exclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof. "up", "down", "left", "right" and the like are used only to indicate a relative positional relationship, and when the absolute position of the object to be described is changed, the relative positional relationship may be changed accordingly.
In the prior art, the high-integration-level large-scale three-party platform still has the following technical defects in actual application: with more and more third party platforms in butt joint, the system design and business logic writing of the high-integration-level large-scale three party platform are more complex. When the tenant is in butt joint with the software platform, the high-integration large-scale three-party platform is still carried out in a traditional code writing mode, so that the technical problems of complex butt joint and low butt joint efficiency of multiple tenants and multiple third-party platforms are caused. The present embodiment is directed to a docking method of a universal three-party access platform to improve the technical drawbacks described above.
The following describes a docking method of the universal three-way access platform according to the present embodiment with reference to the accompanying drawings.
As shown in fig. 1, the docking method includes:
step S102, extracting first elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the first elements.
In a specific implementation, the first element includes: platform name, platform address, platform identification, and platform grouping. Specifically, the platform name is used for identifying a corresponding third party platform by a tenant in the general three-party access platform, the platform address is used for identifying an API prefix of the corresponding third party platform by the general three-party access platform, the platform identifier is used for identifying the same type of third party platform by the general three-party access platform, and the platform grouping is used for distinguishing mutually exclusive same type of third party platforms by the general three-party access platform.
As a specific implementation, the first element includes only a platform name, a platform address, and a platform identifier; and not to platform grouping. At this time, the corresponding application scenario provides for the universal three-party access platform to pre-configure only one third-party platform of a corresponding type. Such as a payment platform, an internet card management platform, etc.
Specifically, the tenant described in this embodiment may include one specific user or member, or may include multiple specific users or members.
Step S104, building tenant access configuration of the general three-party access platform based on second elements carried by each tenant.
In a specific implementation, the second element includes: access name, access status, account key, and target platform. Specifically, the access name is used for tenant identification by the general three-party access platform, the access state is used for controlling access opening or access closing of tenants by the general three-party access platform, the account key is used for authorizing authentication of the tenants by the general three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the general three-party access platform.
And if the platform address is filled, accessing the third party platform interface preferentially through the API prefix splicing path. It is important to note that the API address path accessed may be dynamically assigned for compatibility with some third party platforms. Thus, we have this field (i.e. the second element) redundant in the access configuration, and do not have to fill in by default. If not, the API prefix address configured by the general three-party access platform is directly used. If the API prefix address is configured in the access configuration, the address in the access configuration is preferentially used to complete the API call.
And step S106, realizing the butt joint of the tenant and a target third party platform in the general three party access platform based on the access configuration.
Considering that under partial scenes, a part of third party platforms of general classes for tenants give the maximum authority of the general party access platform at one time to perform global unified access to all tenants; and further, the complexity of independently completing the docking with the third party platform by each tenant is avoided. As shown in fig. 2, the step S102 may further be:
and step S102', extracting third elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the third elements.
In a specific implementation, the third element includes: global access and authentication information. In this embodiment, the global access is used for the universal three-party access platform to open corresponding third-party platforms for all tenants, and the authentication information is used for the universal three-party access platform to perform access authentication on the third-party platforms that are pre-opened for all tenants.
At this time, based on step S102-step S106, the access of the third party platform and the tenant is abstracted. Meanwhile, the requirement of global unified access is considered, and a third element of a third party platform with global access requirement is extracted pertinently; to implement abstract processing of such third party platforms. And furthermore, when the tenant is accessed to the corresponding third party platform based on the general three-party access platform, the quick docking of the tenant and the third party platform can be realized based on the corresponding element acquisition matching.
In summary, the service logic between the pre-configuration and the access configuration of the user side carding platform is as follows: the universal three-party access platform involves docking of multiple third party platforms. And in the general three-party access platform, members in the tenant can maintain respective access configurations, and when the members complete the configuration of the access configuration of the related three-party platform, the members can dock with the corresponding third-party platform. (if the access configuration belongs to the global configuration, an administrator of the general three-party access platform will uniformly maintain the platform information and the access configuration, and meanwhile, for the global configuration, the business of each tenant at the downstream will uniformly be connected to the service of the third party platform, and the access information of the third party platform can be shown in each tenant access configuration in a default way. The platform super manager maintains platform grouping and other information. An intra-tenant administrator maintains the access configuration of the tenant.
Once the third party platform is successfully accessed, the members in the tenant can finish the use of the downstream service. Based on the service implementation, we further explore the corresponding downstream service access architecture after the access method. The platform adopts a micro-service architecture and relates to various service components, such as a route distinguishing component, a three-party authorization component, an RPC interceptor and an adaptation processor. The route distinguishing component mainly aims at providing service route distinguishing support for the same group of third party platforms during service processing. The three-party authorization component mainly provides unified authorization and token service framework, and can rapidly complete authorization service realization only by simple expansion interface adaptation. The RPC interceptor expands the self-service logic by means of the current main stream RPC framework; the method mainly comprises the steps of intercepting, entering a fit general authorization logic and calling an adaptation logic by a three-way interface. The adaptation processor mainly defines a plurality of annotation interfaces and consists of an authorization interface and a service interface, and of course, the adaptation processor unifies an access specification and can be accessed only according to the specification when a developer realizes the adaptation. At the moment, the realization difficulty of accessing the three-party platform is simplified, and a unified access interface mode is provided for the service. Based on this, the embodiment also provides a service docking method of the universal three-party access platform, so that tenants can complete relevant downstream service expansion aiming at the third-party platform.
The following describes a service docking method of the universal three-party access platform according to the present embodiment with reference to the accompanying drawings.
As shown in fig. 3, the service docking method includes:
step S202, obtaining a service request of a tenant.
In this embodiment, the service request is used to request to obtain any service corresponding to any accessed third party platform by the tenant. Specifically, the service request includes service inquiry, service modification, and the like.
As a specific embodiment, as shown in fig. 4, the following steps are further included to perform preprocessing of the service request after step S202:
and step 203, when the data format and the data content of the service request are judged to be incorrect or missing, returning a correction instruction to the tenant.
In particular embodiments, the correction instructions include data formats or data content that need to be modified. At this time, the validity of the service request can be ensured based on step S203, thereby ensuring the smooth proceeding of the subsequent steps.
Step S204, calling the access configuration of the tenant based on the route distinguishing component and traversing the adaptation processor of the third party platform corresponding to the service to acquire the service interface corresponding to the service.
As a specific embodiment, in order to improve the service request processing efficiency of the tenant and the third party platform, as shown in fig. 5, after step S204, the method further includes:
step S205, store the access configuration of the tenant, and the third party platform corresponding to the service, so as to directly make a call when the tenant re-initiates any service request corresponding to the third party platform.
At this time, step S204 need not be performed again each time the tenant initiates a service request to the third party platform.
Step S206, when judging that the tenant does not acquire the authentication of the third party platform corresponding to the service based on the RPC interceptor, invoking a third party authorization component to authorize and authenticate the tenant based on the pre-configuration information of the third party platform and the access configuration information of the tenant.
Similarly, in order to improve the service request processing efficiency of the tenant and the third party platform, the step S206 further includes:
step S207, obtaining the effective duration of the third party platform authorization of the account corresponding to the authorization authentication, and storing the authorization token obtained by the account key according to the effective duration.
Frequent invocation of the authorization interface can be avoided based on step S207. Specifically, if the effective duration is N hours, the account key is stored for N hours. Re-authorization authentication is required after N hours.
And step S208, returning the service content corresponding to the service request to the tenant.
As another embodiment, based on the access method, when global access is adopted, when it is determined that the third party platform corresponding to the service request is preconfigured to the general party access platform based on the third element, the step of calling the access configuration of the tenant based on the route distinguishing component and traversing the adaptation processor of the third party platform by the third party platform corresponding to the service to obtain the service interface corresponding to the service is skipped.
Meanwhile, as a special implementation manner, when the first element does not include a platform group (i.e., the general-purpose three-party access platform specifies that only one corresponding type of third-party platform is preconfigured), step S204 is not required to be executed when a specific service access is performed (i.e., routing discrimination is not required to perform the operation of traversing each service interface of the third-party platform under the same group). At this time, a certain type of service request is defaulted to be only realized on a certain specified third party platform.
In summary, the scheme described in this embodiment is based on a large and medium-sized universal three-way access platform, and has the characteristic of low coupling. The method has the characteristic functions of unified routing judgment, authentication and authorization and the like, and avoids the problems of realizing judgment logic and the like of routing, authentication and the like repeatedly each time; has the advantage of simple operation by hands. Meanwhile, the simple style of the interface is unified, and the code and the implementation difficulty are reduced; the effect of realizing multiple multiplexing at one time is achieved.
The above-described programs may be run on a processor or may also be stored in a memory (or referred to as a computer-readable storage medium), including both permanent and non-permanent, removable and non-removable media, and information storage may be implemented by any method or technique. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable storage media, as defined herein, does not include transitory computer-readable media, such as modulated data signals and carrier waves.
These computer programs may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart block or blocks and/or block diagram block or blocks, and corresponding steps may be implemented in different modules.
Based on the above, the embodiment also provides a docking system of the universal three-party access platform. As shown in fig. 7, the docking system includes:
the first configuration module is used for extracting first elements carried by each third party platform so as to pre-configure each third party platform to the universal three party access platform based on the first elements.
Wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; the platform name is used for the general three-party access platform to identify the corresponding third-party platform, the platform address is used for the general three-party access platform to confirm the API prefix of the corresponding third-party platform, the platform identification is used for the general three-party access platform to confirm the same type of third-party platform, and the platform grouping is used for the general three-party access platform to distinguish mutually exclusive same type of third-party platforms.
And the interface construction module is used for constructing tenant access configuration of the general three-party access platform based on the second elements carried by each tenant.
Wherein the second element comprises: access name, access status, account key, target platform; the access name is used for tenant identification of the universal three-party access platform, the access state is used for controlling access opening or access closing of tenants by the universal three-party access platform, the account key is used for authorizing authentication of the tenants by the universal three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the universal three-party access platform.
And the docking module is used for realizing docking of the tenant and a target third party platform in the general three party access platform based on the access configuration.
Since the docking system is implemented based on the docking method, the docking method described above is already described, and will not be described here.
For example, to implement a global unified access function, the docking system further comprises:
and the second configuration module is used for extracting third elements carried by each third party platform so as to pre-configure each third party platform to the universal three party access platform based on the third elements.
Wherein the third element comprises: global access and authentication information; and the global access is used for the universal three-party access platform to open corresponding third-party platforms for all tenants, and the authentication information is used for the universal three-party access platform to perform access authentication on the third-party platforms which are pre-opened for all tenants.
Similarly, the embodiment also provides electronic equipment. As shown in fig. 8, the electronic device includes at least one processor coupled to a memory, the memory having stored therein a computer program configured to perform the docking method when executed by the processor.
Meanwhile, the embodiment also provides a computer readable storage medium, on which a computer program is stored, the computer program being used for executing the docking method.
While the invention has been described with reference to preferred embodiments, it is not intended to be limiting. Those skilled in the art will appreciate that various modifications and adaptations can be made without departing from the spirit and scope of the present invention. Accordingly, the scope of the invention is defined by the appended claims.
Claims (10)
1. The docking method of the universal three-party access platform is characterized by comprising the following steps of:
extracting first elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the first elements;
wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; the platform name is used for identifying a corresponding third party platform by a tenant in the general three-party access platform, the platform address is used for identifying an API prefix of the corresponding third party platform by the general three-party access platform, the platform identifier is used for identifying the same type of third party platform by the general three-party access platform, and the platform grouping is used for the general three-party access platform to distinguish mutually exclusive same type of third party platforms;
building tenant access configuration of the universal three-party access platform based on second elements carried by each tenant;
wherein the second element comprises: access name, access status, account key and target platform; the access name is used for tenant identification of the universal three-party access platform, the access state is used for controlling access opening or access closing of tenants by the universal three-party access platform, the account key is used for authorizing authentication of the tenants by the universal three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the universal three-party access platform;
and realizing the butt joint of the tenant and a target third party platform in the general three party access platform based on the access configuration.
2. The docking method of the universal three-party access platform according to claim 1, wherein the first element carried by each third-party platform is extracted, so that each third-party platform is preconfigured to the universal three-party access platform based on the first element; further comprises:
extracting third elements carried by each third party platform, and pre-configuring each third party platform to the universal three party access platform based on the third elements;
wherein the third element comprises: global access and authentication information; and the global access is used for the universal three-party access platform to open corresponding third-party platforms for all tenants, and the authentication information is used for the universal three-party access platform to perform access authentication on the third-party platforms which are pre-opened for all tenants.
3. A service docking method of a universal three-party access platform, characterized in that the docking method based on claim 1 comprises:
acquiring a service request of a tenant; the service request is used for requesting to acquire any service corresponding to any accessed third party platform by the tenant;
calling the access configuration of the tenant based on a route distinguishing component and a third party platform corresponding to the service to traverse an adaptation processor of the third party platform so as to acquire a service interface corresponding to the service;
when judging that the tenant does not acquire authentication of a third party platform corresponding to the service based on the RPC interceptor, calling a third party authorization component to authorize and authenticate the tenant based on the pre-configuration information of the third party platform and the access configuration information of the tenant;
and returning the service content corresponding to the service request to the tenant.
4. The method for interfacing services of a universal three-party access platform according to claim 3, wherein the routing discriminant component invokes the access configuration of the tenant and the third-party platform corresponding to the service to traverse the adaptation processor of the third-party platform to obtain a service interface corresponding to the service; comprising the following steps:
storing the access configuration of the tenant and a third party platform corresponding to the service to directly call when the tenant reinitiates any service request corresponding to the third party platform.
5. The service docking method of the universal three-party access platform according to claim 3, wherein after obtaining the service request of the tenant, the method comprises:
and when the third party platform corresponding to the service request is pre-configured to the universal three-party access platform based on the third element, skipping the step of calling the access configuration of the tenant based on the route distinguishing component and traversing the adaptation processor of the third party platform by the third party platform corresponding to the service so as to acquire the service interface corresponding to the service.
6. The service docking method of the universal three-party access platform according to claim 3 or 4, wherein when the RPC-based interceptor judges that the tenant does not acquire authentication of a third-party platform corresponding to the service, a three-party authorization component is invoked to perform authorization authentication on the tenant based on pre-configuration information of the third-party platform and access configuration information of the tenant; comprising the following steps:
and acquiring the effective duration of the third party platform authorization of the account corresponding to the authorization authentication, and storing the authorization token acquired by the account key according to the effective duration.
7. A docking system for a universal three-way access platform, comprising:
the first configuration module is used for extracting first elements carried by each third party platform so as to pre-configure each third party platform to the universal three party access platform based on the first elements;
wherein the first element comprises: platform name, platform address, platform identification, and platform grouping; the platform name is used for identifying a corresponding third party platform by a tenant in the general three-party access platform, the platform address is used for identifying an API prefix of the corresponding third party platform by the general three-party access platform, the platform identifier is used for identifying the same type of third party platform by the general three-party access platform, and the platform grouping is used for the general three-party access platform to distinguish mutually exclusive same type of third party platforms;
the interface construction module is used for constructing tenant access configuration of the general three-party access platform based on second elements carried by each tenant;
wherein the second element comprises: access name, access status, account key, target platform; the access name is used for tenant identification of the universal three-party access platform, the access state is used for controlling access opening or access closing of tenants by the universal three-party access platform, the account key is used for authorizing authentication of the tenants by the universal three-party access platform, and the target platform is used for confirming a third-party platform selected by the tenants by the universal three-party access platform;
and the docking module is used for realizing docking of the tenant and a target third party platform in the general three party access platform based on the access configuration.
8. The docking system for a universal three-way access platform of claim 7, comprising:
the second configuration module is used for extracting third elements carried by each third party platform so as to pre-configure each third party platform to the universal three party access platform based on the third elements;
wherein the third element comprises: global access and authentication information; and the global access is used for the universal three-party access platform to open corresponding third-party platforms for all tenants, and the authentication information is used for the universal three-party access platform to perform access authentication on the third-party platforms which are pre-opened for all tenants.
9. An electronic device comprising at least one processor coupled to a memory, the memory having stored therein a computer program configured to perform the method of any of claims 1-2 when executed by the processor.
10. A computer readable storage medium, characterized in that a computer program is stored thereon for executing the method of any of the claims 1-2.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311152580.1A CN116886763A (en) | 2023-09-08 | 2023-09-08 | Butt joint method, service butt joint method and system of universal three-party access platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311152580.1A CN116886763A (en) | 2023-09-08 | 2023-09-08 | Butt joint method, service butt joint method and system of universal three-party access platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116886763A true CN116886763A (en) | 2023-10-13 |
Family
ID=88268461
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311152580.1A Pending CN116886763A (en) | 2023-09-08 | 2023-09-08 | Butt joint method, service butt joint method and system of universal three-party access platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116886763A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180034924A1 (en) * | 2016-07-28 | 2018-02-01 | Polybit Inc. | System and method for a unified interface to networked webservices |
| US20180146049A1 (en) * | 2016-11-22 | 2018-05-24 | International Business Machines Corporation | Capturing configuration items from hybrid-cloud provisioning data |
| US11057315B1 (en) * | 2020-01-06 | 2021-07-06 | International Business Machines Corporation | Generating a scaling plan for external systems during cloud tenant onboarding/offboarding |
| WO2022240906A1 (en) * | 2021-05-11 | 2022-11-17 | Strong Force Vcn Portfolio 2019, Llc | Systems, methods, kits, and apparatuses for edge-distributed storage and querying in value chain networks |
| CN115426147A (en) * | 2022-08-29 | 2022-12-02 | 济南浪潮数据技术有限公司 | Cloud platform service access method, system, equipment and storage medium |
| WO2023071305A1 (en) * | 2021-10-28 | 2023-05-04 | 青岛海尔科技有限公司 | Cloud database resource processing method and apparatus, and electronic device and storage medium |
| WO2023092316A1 (en) * | 2021-11-24 | 2023-06-01 | 国云科技股份有限公司 | Third-party service login method and apparatus, terminal device, and storage medium |
-
2023
- 2023-09-08 CN CN202311152580.1A patent/CN116886763A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180034924A1 (en) * | 2016-07-28 | 2018-02-01 | Polybit Inc. | System and method for a unified interface to networked webservices |
| US20180146049A1 (en) * | 2016-11-22 | 2018-05-24 | International Business Machines Corporation | Capturing configuration items from hybrid-cloud provisioning data |
| US11057315B1 (en) * | 2020-01-06 | 2021-07-06 | International Business Machines Corporation | Generating a scaling plan for external systems during cloud tenant onboarding/offboarding |
| WO2022240906A1 (en) * | 2021-05-11 | 2022-11-17 | Strong Force Vcn Portfolio 2019, Llc | Systems, methods, kits, and apparatuses for edge-distributed storage and querying in value chain networks |
| WO2023071305A1 (en) * | 2021-10-28 | 2023-05-04 | 青岛海尔科技有限公司 | Cloud database resource processing method and apparatus, and electronic device and storage medium |
| WO2023092316A1 (en) * | 2021-11-24 | 2023-06-01 | 国云科技股份有限公司 | Third-party service login method and apparatus, terminal device, and storage medium |
| CN115426147A (en) * | 2022-08-29 | 2022-12-02 | 济南浪潮数据技术有限公司 | Cloud platform service access method, system, equipment and storage medium |
Non-Patent Citations (1)
| Title |
|---|
| 张桢;高宏;: "多云异构环境下统一云管平台设计研究", 中国新通信, no. 11 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110096857B (en) | Authority management method, device, equipment and medium for block chain system | |
| US10938924B1 (en) | Systems and methods related to executing transactions in a hybrid cloud environment | |
| US11392675B2 (en) | Request authorization using recipe-based service coordination | |
| US9270703B1 (en) | Enhanced control-plane security for network-accessible services | |
| US20120296960A1 (en) | Method and system for providing access to mainframe data objects in a heterogeneous computing environment | |
| US10924587B1 (en) | Live migration for highly available data stores | |
| CN107580032B (en) | Data processing method, device and equipment | |
| CN109359449B (en) | Authentication method, device, server and storage medium based on micro service | |
| CN108595451A (en) | Service request processing method and device | |
| CN103118073A (en) | Virtual machine data persistence storage system and method in cloud environment | |
| CN112329001B (en) | Data distribution method, system, terminal and medium between internal network and external network | |
| CN109542590A (en) | The method of virtual Socket communication under Docker cluster multi-tenant | |
| CN114020444B (en) | Calling system and method for resource service application in enterprise digital middle station | |
| CN110070360A (en) | A kind of transactions requests processing method, device, equipment and storage medium | |
| CN112328363B (en) | Cloud hard disk mounting method and device | |
| CN109819020A (en) | Third-party platform based on configurationization logs in interconnection method, storage medium | |
| CN116886763A (en) | Butt joint method, service butt joint method and system of universal three-party access platform | |
| US9723436B2 (en) | Mobile device location | |
| US11842211B2 (en) | Method and system for collecting user information according to usage of provided virtual desktop infrastructure service | |
| US11343352B1 (en) | Customer-facing service for service coordination | |
| CN113704123B (en) | Interface testing method, device, equipment and storage medium | |
| CN112367661B (en) | USAT application matching implementation method, USIM, terminal, device and medium | |
| CN114170007A (en) | Orthogonal easy return message assembly method, program product, medium, and electronic device | |
| CN113986995A (en) | Request distribution method and device, storage medium and electronic equipment | |
| JP2022553696A (en) | geometric cross-component filtering |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |