Search

CN-121979562-A - Enterprise portal integration method based on user-defined client

CN121979562ACN 121979562 ACN121979562 ACN 121979562ACN-121979562-A

Abstract

The invention relates to the technical field of computer software, and discloses an enterprise portal integration method based on a user-defined client, wherein a desktop system and a server system cooperatively execute. The desktop end system performs signature verification and static compilations verification on the integrated recipe packages, activates candidate integrated recipe packages when the integrated recipe packages pass, rolls back and activates the last effective integrated recipe package when any one fails, performs constraint compiling on a precondition expression set and a sequential state machine definition, calculates a satisfaction accessibility relation, performs consistency judgment on the desktop end system based on a verifiable credential package and a target authority range, outputs an entry permission or rejection and a reason code, performs recipe version, interface contract abstract and sequential state verification on ticket application parameters, then issues a disposable link ticket carrying use_once, generates a receipt abstract and an idempotent event key, writes the receipt abstract into an event account book, and performs batch compensation uploading when offline and network recovery are performed.

Inventors

  • JIANG DONGPO

Assignees

  • 淮安东创兴科科技有限公司

Dates

Publication Date
20260505
Application Date
20260120

Claims (10)

  1. 1. The enterprise portal integration method based on the user-defined client side is characterized in that the method is cooperatively executed by a desktop end system serving as a unified portal of a user and a server end system providing the capabilities of issuing a formula and issuing notes, and the server end system performs information interaction with an enterprise business system and an enterprise service bus; The desktop end system is used as a front end unified entrance of the client end portal system and is used for providing a portal entrance interface and bearing business page access, and is used for fixedly displaying an activation formula version identifier, an online state and an offline queue number at the top of the interface and displaying a reject reason code and a disposal action entrance when judging that the client end portal system does not pass or the bill reject occurs.
  2. 2. The customized client-based enterprise portal integration method of claim 1, wherein the desktop system, when executing the method, further executes the following modules: The system comprises a recipe acquisition and activation module, a candidate integrated recipe package, a signature verification module, a static compiling module and a verification module, wherein the recipe acquisition and activation module is used for acquiring an integrated recipe package from a server system and executing signature verification and static compiling verification on the integrated recipe package, activating the integrated recipe package when verification passes, and backing and activating a last valid integrated recipe package when verification fails; the constraint compiling and accessibility judging module is used for executing constraint compiling on the pre-condition expression set obtained by analyzing the activated integrated recipe package and the definition of the sequential state machine, constructing a constraint session diagram and calculating a satisfaction accessibility relation; The credential management module is used for executing statement aggregation and binding factor determination on the client authentication result, generating a verifiable credential package and calculating a credential package abstract; The entrance checking and disposing module is used for executing reachability judgment based on the satisfaction reachability relation and consistency judgment based on the verifiable credential package and the authority range of the target service system when the user triggers the target entrance, allowing continuous access when both the two judgments pass, and executing disposing action according to the reject reason code and disposing action mapping defined by the activated integrated recipe package when either one of the judgments does not pass; The bill interaction and sequence control module is used for submitting bill application parameters to the server system and receiving the disposable link bill when the disposable link bill is indicated by the activated integrated formula package, executing state transition judgment according to the sequence state machine, attaching the disposable link bill to a target request when the judgment is passed, triggering a sequence replenishment flow when the judgment is not passed, wherein the value range of a triggering threshold value X of the replenishment flow is 30-300 seconds, the value range of the maximum replenishment times N_max is 1-5 times, enabling the sequence state machine to enter an allowable issuing state or a termination state when the replenishment is successful, and executing treatment action limited by the activated integrated formula package when the replenishment is failed; And the event ledger and compensation synchronization module is used for generating a response piece abstract and an idempotent event key after completing a target request, writing the response piece abstract and the idempotent event key into the event ledger, executing offline account entry when a network is unavailable, executing compensation uploading according to batches when the network is recovered, and completing a conflict disposal closed loop according to a conflict disposal rule defined by an activated integrated formula package.
  3. 3. The enterprise portal integration method based on user-defined client side of claim 1, wherein the server side system is configured to receive a recipe acquisition request and a ticket application request submitted by the desktop side system, and perform: The formula release process is used for generating and issuing an integrated formula package containing a formula version identifier, a formula signature and a formula serialization byte sequence; The contract registration process is used for registering the interface contract abstract of the business system and providing contract consistency check basis for the bill issuing process; The bill issuing process is used for executing recipe version permission verification, interface contract abstract consistency verification and sequential state permission verification on bill application parameters, issuing a disposable link bill when verification is passed, and returning a reject reason code when verification is not passed; the disposable link ticket carries a single-use mark use_once, and the valid period ott _ttl takes a value ranging from 30 seconds to 300 seconds.
  4. 4. The enterprise portal integration method based on the user-defined client of claim 1, wherein the integrated recipe package at least writes the following fields including a recipe version identifier, a service system description record table, a set of pre-conditional expressions, a sequential state machine definition, a set of reject reason codes, a reject reason code to process action map table, a recipe serialization byte sequence R_bytes, and a recipe signature, the service system description record table at least includes a service system identifier, an ingress route identifier, a set of authority ranges, an interface contract summary, and a jump constraint parameter.
  5. 5. The custom client-based enterprise portal integration method of claim 1, wherein the recipe acquisition and activation module performs at least the following checks when performing a static compilable check on an integrated recipe package: Checking is only allowed to be performed on the precondition expression by using a limiting predicate set, wherein the limiting predicate set at least comprises predicates such as a token existence predicate has_token (app_id), a scope of authority comprises predicate scope_has (scope), a binding factor consistent predicate bind_ok (factor), a recipe version consistent predicate ver_eq (reverse_ver), and an interface contract summary consistent predicate composition_eq (contact_hash); Performing a check on at least an initial state and a termination state of the sequential state machine; Performing a check on the state transition condition as a determinable condition; And performing verification on that the reject cause code set is limited enumeration and that the reject cause code does not have a missing key in the processing action mapping table.
  6. 6. The enterprise portal integration method based on the user-defined client side of claim 1, wherein when the constraint compiling and reachability determination module constructs a constraint session graph, a business system is taken as a node, a precondition expression set and jump constraint are taken as side constraints, and the satisfiability reachability relation is obtained by judging all precondition expressions on a path item by item and outputting a binary reachability result.
  7. 7. The enterprise portal integration method based on the user-defined client side of claim 1, wherein when the credential management module generates the verifiable credential package, at least writing a token set, a statement set and a binding factor, wherein the statement set at least writes a user identifier, an organization identifier, a role set, a permission range set and an expiration time; The chain type abstract is obtained by performing hash operation after splicing the formula version identifier, the user identifier, the token set, the statement set and the binding factor according to a deterministic sequence.
  8. 8. The custom client-based enterprise portal integration method of claim 1, wherein the portal verification and handling module performs two decisions when the user triggers the target portal that satisfy: The reachability judgment basis can output the satisfaction reachability relation as pass or fail; the consistency judgment is obtained by calculating an intersection of the authority range set in the verifiable credential package and the authority range set of the target service system, the intersection is judged to pass when the intersection is not empty, and the intersection is judged to not pass when the intersection is empty; When any one of the determinations is not passed, the disposing action value is defined as re-pulling the integrated recipe package, re-authenticating, returning to the last valid integrated recipe package, triggering the sequential replenishment flow, prohibiting the ticket application, and determining by the reject reason code from the disposing action mapping table.
  9. 9. The enterprise portal integration method based on the user-defined client side of claim 1, wherein the ticket application parameters submitted to the server side system by the ticket interaction and sequence control module at least carry a recipe version identification, a target service system interface contract abstract, a credential package abstract, a sequence constraint identification and a current sequence state.
  10. 10. The enterprise portal integration method based on the user-defined client according to claim 1, wherein when the event ledger and compensation synchronization module generates an idempotent event key, the event ledger and compensation synchronization module is obtained by calculating a user identifier, a service system identifier, a target path and a time window starting time stamp, wherein the time window width is in a range of 10 seconds to 120 seconds; when the same idempotent event keys exist in the event ledger, the idempotent overlay rule is defined as that the old record is only updated when the client time stamp of the new record is larger than that of the old record, otherwise, the old record is kept unchanged; And executing compensation uploading according to batches during network recovery, wherein the compensation uploading is executed according to batches, the range of batch size values is 50-500, the constraint of the enqueue of the compensation queue is defined as allowing the enqueue uploading only when the sequential state machine of the corresponding record is in a finished state, the conflict judgment condition is defined as that idempotent event keys are the same and the response piece abstracts are different, and the conflict disposal rule is defined as 'based on a newer client time stamp' or 'based on a server authority response piece', and is determined by an enumeration value issued by an activated integrated formula package.

Description

Enterprise portal integration method based on user-defined client Technical Field The invention relates to the technical field of computer software, in particular to an enterprise portal integration method based on a user-defined client. Background In the enterprise informatization construction process, a plurality of service systems are usually operated at the same time, and cross-system data exchange and service coordination are realized through an enterprise service bus. In order to reduce the operation cost of switching among a plurality of service systems, an enterprise portal mode is often adopted in the prior art to provide a unified entry, wherein one common implementation is that a desktop end system or a custom client is used as a front-end entry, different service systems are accessed through an embedded page, a browser window is popped up or an interface is called, and the service end system is responsible for communication interaction with an enterprise service bus and each service system, so that the capabilities of message pushing, notification to be done, unified login and the like are provided for the desktop end system. The prior art still has a plurality of technical limitations in the actual deployment and operation and maintenance processes. Firstly, portal access and business system access rules are usually maintained by configuration files or background management interfaces, but configuration content often lacks expression constraint capable of being judged by a machine, and judgment of portal accessibility, precondition satisfaction and cross-system jump sequence by a desktop end system during operation depends on manual appointments or decentralized logic, so that when the business system is increased or decreased, the authority range is adjusted or the interface caliber is changed, the desktop end system may have the conditions that portal display is inconsistent with an actual accessible state, a unified disposal path is lacking after cross-system jump failure and the like. In the absence of unified constraint and consistency verification, the situation that the token is not matched with the authority range of a target system, the parameters or the return structure are inconsistent due to interface contract change, and the rejection is caused by repeated use or overtime use of ticket jump parameters, thereby further causing the request failure of a user side and causing repeated operation easily occurs. Thirdly, the portal system often needs to mark the user operation, the jump result and the notification processing process to support audit and problem positioning, but under the network fluctuation or offline scene, the operation record at the client side and the receiving result at the server side are possibly inconsistent, and when idempotent constraint and conflict judgment conditions are absent, repeated submission, repeated account entry or conflict record are easy to cause and difficult to automatically process, so that the operation and maintenance processing cost is increased. Therefore, there is still room for improvement in the existing enterprise portal integration method in terms of "portal rule determinability, cross-system access consistency, jump sequence controllability, and record consistency in offline and network recovery scenarios", and an enterprise portal integration method capable of adapting a custom client as a unified portal and forming a certain interaction constraint between a server and a client is needed. The invention provides an enterprise portal integration method based on a user-defined client side, which is cooperatively executed by a desktop side system and a server side system, wherein the server side system issues an integrated recipe package and issues a disposable link bill, the desktop side system executes signature verification and static compilable verification on the integrated recipe package to determine an activated integrated recipe package, builds a constraint session diagram based on the activated integrated recipe package, calculates a satisfiability relation to complete entrance reachability judgment and authority consistency judgment, the server side system executes verification of recipe version, interface contract abstract and sequential state on bill application parameters in a bill required scene, issues a disposable link bill which carries a single-use mark and has a valid period, and the desktop side system generates a receipt abstract and an idempotent event key to write in an event account book after completing a target request, and executes compensation uploading and conflict treatment in batches in an offline and network recovery scene. Disclosure of Invention Aiming at the defects of the prior art, the invention provides an enterprise portal integration method based on a user-defined client to solve the problems in the background art. The desktop end system as user unified entrance cooperates with the server end syste