CN111443958A - Interface display method and system - Google Patents
Interface display method and system Download PDFInfo
- Publication number
- CN111443958A CN111443958A CN202010217522.2A CN202010217522A CN111443958A CN 111443958 A CN111443958 A CN 111443958A CN 202010217522 A CN202010217522 A CN 202010217522A CN 111443958 A CN111443958 A CN 111443958A
- Authority
- CN
- China
- Prior art keywords
- interface
- subsystem
- target subsystem
- target
- data
- 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 37
- 238000011161 development Methods 0.000 claims abstract description 43
- 230000001960 triggered effect Effects 0.000 claims abstract description 11
- 230000005540 biological transmission Effects 0.000 claims description 35
- 238000003860 storage Methods 0.000 claims description 14
- 238000004590 computer program Methods 0.000 claims description 10
- 150000003839 salts Chemical class 0.000 claims description 7
- 230000006870 function Effects 0.000 description 13
- 238000009877 rendering Methods 0.000 description 11
- 238000004891 communication Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 238000013459 approach Methods 0.000 description 2
- 238000006243 chemical reaction Methods 0.000 description 2
- 230000014759 maintenance of location Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 230000003068 static effect Effects 0.000 description 2
- 102220517403 DNA excision repair protein ERCC-6_S10A_mutation Human genes 0.000 description 1
- 102220517404 DNA excision repair protein ERCC-6_S10D_mutation Human genes 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 238000010295 mobile communication Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000008520 organization Effects 0.000 description 1
- 230000003252 repetitive effect Effects 0.000 description 1
- 102200082907 rs33918131 Human genes 0.000 description 1
- 238000012360 testing method Methods 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
- G06F21/46—Structures or tools for the administration of authentication by designing passwords or checking the strength of passwords
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- Computer Hardware Design (AREA)
- Human Computer Interaction (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The invention discloses an interface display method, which comprises the following steps: receiving a target subsystem page loading instruction triggered by a user; acquiring a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, wherein the configuration file comprises a development type, configuration data and a loading address of the target subsystem; if the development type is an Iframe nested type, acquiring a subsystem interface corresponding to the target subsystem according to the loading address, and filling the configuration data into the subsystem interface to obtain a display interface; if the development type is a non-Iframe nested type, acquiring an API (application programming interface) corresponding to the target subsystem according to the loading address; and receiving the drawing data returned by the target subsystem through the API interface, and drawing an interface according to the drawing data and the configuration data to obtain a display interface. The invention has the advantages that different pages customized according to different requirements can be distributed and displayed in a more flexible mode.
Description
Technical Field
The embodiment of the invention relates to the field of Internet technology application, in particular to an interface display method and system.
Technical Field
Currently, there are many systems on the market, especially OA systems, with many cards on the workbench, but these systems are generally one system, and both data source and card definition are done by OA systems.
When the client determines the layout of the displayed page, in the prior art, the layout design of typesetting, color matching and the like of different contents in the page can be determined first, then the corresponding layout is realized by writing codes, and finally the page to be displayed can be released through various tests. For the published page, a browser or a client at the front end can send a page request to a server at the rear end, and the rear end can directly return page data, so that the front end can lay out and display the page according to the page data. However, when multiple systems are integrated, each subsystem needs its own card to correspond to different pages, and is allocated to different people, which is difficult to be realized for the original subsystem with single configuration.
Disclosure of Invention
In view of this, an object of the embodiments of the present invention is to provide an interface display method and system, which can layout and display different pages customized according to different requirements in a more flexible manner.
In order to achieve the above object, an embodiment of the present invention provides an interface display method, including:
receiving a target subsystem page loading instruction triggered by a user;
acquiring a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, wherein the configuration file comprises a development type, configuration data and a loading address of the target subsystem;
judging whether the development type is an Iframe nested type or a non-Iframe nested type;
if the development type is an Iframe nested type, acquiring a subsystem interface corresponding to the target subsystem according to the loading address, and filling the configuration data into the subsystem interface to obtain a display interface of the target subsystem;
if the development type is a non-Iframe nested type, acquiring an API (application programming interface) corresponding to the target subsystem according to the loading address;
and receiving the drawing data returned by the target subsystem through the API interface, and drawing an interface according to the drawing data and the configuration data to obtain a display interface of the target subsystem.
Further, before the receiving a target subsystem page load instruction triggered by a user, the method includes:
receiving a login instruction of the user;
acquiring a main interface of a workbench according to the login instruction, wherein the main interface of the workbench comprises a subsystem card list;
receiving a configuration instruction of a target subsystem card selected by the user in the subsystem card list;
and generating a configuration file corresponding to the target subsystem card according to the configuration instruction.
Further, the obtaining of the subsystem interface corresponding to the target subsystem according to the load address includes:
a subsystem gateway linking the subsystem interface through the loading address;
receiving an authentication result of the subsystem gateway authenticating the loading address through single sign-on;
and if the authentication result is that the authentication is passed, acquiring a subsystem interface corresponding to the target subsystem.
Further, before the obtaining the API interface corresponding to the target subsystem according to the load address, the method includes:
acquiring a key of a system account currently logged in by the user;
and uploading the secret key to the target subsystem so that the target subsystem takes the secret key as an encrypted salt value, and encrypting the drawing data by adopting the salt value to obtain transmission data.
Further, the receiving drawing data returned by the target subsystem through the API interface includes:
and receiving the drawing data obtained by decrypting the transmission data through the API by the target subsystem.
Further, the receiving drawing data returned by the target subsystem through the API interface includes:
acquiring a transmission format of the API;
and receiving the drawing data transmitted by the target subsystem through the API according to the transmission format.
Further, the interface drawing according to the drawing data and the configuration data to obtain the display interface of the target subsystem includes:
calling an Echarts component to carry out graphic drawing on the drawing data;
and performing interface filling on the drawn graph by the configuration data to obtain a display interface of the target subsystem.
In order to achieve the above object, an embodiment of the present invention further provides an interface display system, including:
the receiving module is used for receiving a target subsystem page loading instruction triggered by a user;
the first acquisition module is used for acquiring a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, wherein the configuration file comprises the development type, the configuration data and the loading address of the target subsystem;
the judging module is used for judging whether the development type is an Iframe nested type or a non-Iframe nested type;
a second obtaining module, configured to, if the development type is an Iframe nested type, obtain a subsystem interface corresponding to the target subsystem according to the load address, and fill the configuration data in the subsystem interface to obtain a display interface of the target subsystem;
a third obtaining module, configured to obtain, if the development type is a non-Iframe nested type, an API interface corresponding to the target subsystem according to the load address;
and the drawing module is used for receiving the drawing data returned by the target subsystem through the API interface, and drawing an interface according to the drawing data and the configuration data to obtain a display interface of the target subsystem.
In order to achieve the above object, an embodiment of the present invention further provides a computer device, where the computer device includes a memory and a processor, where the memory stores a computer program that is executable on the processor, and the computer program, when executed by the processor, implements the steps of the interface presentation method described above.
To achieve the above object, an embodiment of the present invention further provides a computer-readable storage medium, in which a computer program is stored, where the computer program is executable by at least one processor, so as to cause the at least one processor to execute the steps of the interface presentation method described above.
According to the interface display method and system provided by the embodiment of the invention, the configuration file in the subsystem page loading instruction of the user is obtained, the development type in the configuration file is judged, whether the development type is an Iframe nested type or not is judged, and if the development type is the Iframe nested type, the subsystem interface corresponding to the loading address can be displayed; if the development type is a non-Iframe nested type, calling a corresponding API (application program interface) to transmit drawing data, and drawing the interface of the drawing data; the client can be enabled to lay out and display different pages customized according to different requirements in a more flexible mode under the condition of less repetitive work.
Drawings
Fig. 1 is a flowchart of an interface display method according to a first embodiment of the present invention.
Fig. 2 is a flowchart of step S10 according to an embodiment of the present invention.
Fig. 3 is a flowchart of step S106 according to an embodiment of the present invention.
Fig. 4 is a flowchart of step S108 according to an embodiment of the present invention.
Fig. 5 is a flowchart of step S107 according to an embodiment of the present invention.
Fig. 6 is a flowchart of step S110 according to an embodiment of the present invention.
Fig. 7 is a schematic view of program modules of a second embodiment of the interface display system according to the present invention.
Fig. 8 is a schematic diagram of a hardware structure of a third embodiment of the computer apparatus according to the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention more apparent, the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and are not intended to limit the invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
Example one
Referring to fig. 1, a flowchart illustrating steps of an interface displaying method according to a first embodiment of the invention is shown. It is to be understood that the flow charts in the embodiments of the present method are not intended to limit the order in which the steps are performed. The following description is made by way of example with the computer device 2 as the execution subject. The details are as follows.
Step S100, receiving a target subsystem page loading instruction triggered by a user.
Specifically, a user selects a target subsystem on a main interface of a workbench, sets the target subsystem, and after the setting is completed, triggers a target subsystem page loading instruction, wherein the target subsystem page loading instruction is used for loading a set display page of the target subsystem, and the target subsystem page loading instruction comprises a system account and a password of the user.
Referring to fig. 2, before the step S100, the method includes a step S10:
and step S10A, receiving a login instruction of the user.
The method comprises the steps that before a subsystem page loading instruction triggered by a user is received, the user logs in a system, when the user fills in a system account and a system password of the user, a login request, the system account and the system password are generated into a login instruction, when the user logs in, the system identifies a label of the user, if the label of the user is a card administrator user, a card list of a main interface is customized according to a preset card template, information such as a subsystem, a UR L and a user label which each card is connected to is configured, if the subsystem also has the card, the card template of the main interface is configured into the card template of a sub-interface of the subsystem, if the label of the user is a non-card administrator user, a corresponding card list is loaded in the main interface according to preset conditions, the non-card administrator user can further set the card list, and the label of the user can be a user type, a user role or an organization to which the user belongs.
And step S10B, acquiring a workbench main interface according to the login instruction, wherein the workbench main interface comprises a subsystem card list.
Specifically, after the user logs in successfully, the system displays a workbench main interface, the workbench main interface comprises a card list preset by the user, and the type of the card is preset. The user can call the configuration file of the card list to set the display type and the display content of each card in the card list; the display type of the card can be as follows: pie charts, bar charts, leaderboards, and the like; the display content of the card can be as follows: calendar, news, to-do tasks, to-do summaries, etc. When the card is defined, a check box is configured to select whether default display is performed, and if the check is performed, matching is performed according to a tag (which may be an account) corresponding to an account of a user, and a card (or a card list) on the tag matching is displayed.
Step S10C, receiving a configuration instruction of a target subsystem card selected by the user in the subsystem card list.
Specifically, a target subsystem card is selected from the subsystem card list, a configuration instruction of the target subsystem card is triggered after the target subsystem card is clicked, the configuration instruction is used for configuring a display page of a target subsystem corresponding to the target subsystem card, and a configuration file of the target subsystem is obtained according to the configuration instruction so as to configure a display interface of the target subsystem corresponding to the target subsystem card.
Step S10D, generating a configuration file corresponding to the target subsystem card according to the configuration instruction.
Specifically, a target subsystem card is defined, which includes the size of the target subsystem card, whether default display is available, the display format of the subsystem, UR L of the data source, and the user label (e.g., whether display is available or not according to the user type, whether user role is available or not, which is extensible), so as to obtain a configuration file
Step S102, obtaining a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, wherein the configuration file comprises the development type, the configuration data and the loading address of the target subsystem.
Specifically, the configuration file is linked to according to a target subsystem page loading instruction, the configuration file is an xml file, the development type is an interface type, the loading address is an address of a corresponding card link, and the configuration data is data which needs to be displayed in the development type by a user.
And step S104, judging whether the development type is an Iframe nesting type or a non-Iframe nesting type.
Specifically, whether the interface type is an Iframe nested type or not is judged, and whether a pre-drawn subsystem interface is called to a current main interface or not is indicated; if the prepared subsystem interface needs to be called, the subsystem interface is an Iframe nested type; if the prepared subsystem interface does not need to be called, the type is a non-Iframe nested type. If the type is a non-Iframe nested type, acquiring corresponding drawing data through an API (application programming interface), and drawing the drawing data according to the set data; if the type is an Iframe nested type, the graphical drawing is not needed, and only the user data is filled into the corresponding subsystem interface. When the original set page needs to be nested into the current page, Iframe nesting can be used, and there are two ways when Iframe nesting is used: 1) direct nesting of other websites does not need to be logged in; 2) acquiring the nested page only when other websites need to be logged in; the embodiment of the present invention employs the second method.
Step S106, if the development type is an Iframe nesting type, acquiring a subsystem interface corresponding to the target subsystem according to the loading address, and filling the configuration data into the subsystem interface to obtain a display interface of the target subsystem.
Specifically, if the development type is an Iframe nested type, a corresponding target subsystem interface is called. When the loading address is linked to the corresponding subsystem interface, the loading address passes through a system gateway of the subsystem interface, and the system gateway authenticates the loading address, wherein the authentication mode is SSO (Single sign on) authentication.
Exemplarily, referring to fig. 3, the step S106 includes:
step S106A, linking the subsystem gateway of the subsystem interface through the loading address.
Specifically, the loading address can be linked with a storage address of the subsystem interface, and the subsystem interface is acquired after passing through the subsystem gateway.
Step S106B, receiving an authentication result of the subsystem gateway authenticating the loading address through single sign-on.
Specifically, the authentication result is whether the authentication load address can pass through the subsystem gateway of the corresponding target subsystem, and the single sign-on is a one-time authentication sign-on by the user. When the user logs in the identity authentication server once, the authority of accessing other associated systems and application software in the single sign-on system can be obtained, and meanwhile, the realization does not need an administrator to modify the login state or other information of the user, which means that in a plurality of application systems, the user can access all mutually trusted application systems only by logging in once. This approach reduces the time consumption resulting from logging in, assists with user management, and is currently popular. To implement the function of SSO, the application system must be able to identify the user who has logged in, by only logging in once. The application system can identify and extract tickets, and can automatically judge whether the current user logs in through communication with the authentication system, so that the single sign-on function is completed.
In addition:
(1) a single user information database is not necessary, many systems cannot store all user information in a centralized manner, and the user information should be allowed to be placed in different storages.
(2) The unified authentication system is not to say that only a single authentication server is provided
When the user accesses the application system 2, the authentication server 2 can recognize that the ticket is generated by the first server, and the function of SSO can still be achieved by exchanging authentication information through a standard communication protocol (for example, SAM L) between the authentication servers.
Step S106C, if the authentication result is that the authentication is passed, acquiring a subsystem interface corresponding to the target subsystem.
Specifically, if the authentication is passed, calling a corresponding subsystem interface, and filling the configuration data into the corresponding subsystem interface to obtain a display interface of the subsystem; and if the SSO authentication is not passed, the corresponding subsystem interface is not called.
And S108, if the development type is a non-Iframe nested type, acquiring an API (application program interface) corresponding to the target subsystem according to the loading address.
Specifically, if the development type is a non-Iframe nested type, the API interface is called to obtain drawing data of the interface, and the load address may be linked to the corresponding API interface.
Exemplarily, the step S108 includes:
and receiving the drawing data obtained by decrypting the transmission data through the API by the target subsystem.
Specifically, before the API interface is called, a key of the system account currently logged in by the user is acquired, and the key and the drawing data are encrypted to obtain transmission data. And when the API interface is called, acquiring the transmission data, transmitting the transmission data through the API interface, and judging whether the API interface can decrypt and verify the transmission data. When decrypting, the key is taken according to the account ID of the system which the user logs in at present, the transmitted data is decrypted, if the decryption is successful, the API interface is proved to be legal, the API interface can return the corresponding data, and if the decryption is failed, the illegal request is called. This ensures that the API interface is not accessed illegally. The safety of the API interface is ensured, and data leakage is prevented. If the API interface successfully decrypts the transmitted data, acquiring drawing data corresponding to the development type; if the API interface does not decrypt the transmitted data successfully, the page loading instruction of the subsystem is represented to be loaded illegally, and the API interface does not transmit the data.
Exemplarily, referring to fig. 4, the step S108 further includes:
step S108A, obtaining the transmission format of the API interface.
Specifically, in the configuration file, the transmission format of the output parameter and the transmission format of the input parameter of the API interface are set, and the transmission format of the output parameter is obtained when data transmission is performed.
Step S108B, receiving the drawing data transmitted by the target subsystem according to the transmission format through the API interface.
Specifically, the API interface returns the drawing data according to the transmission format of the callout on the configuration document without data conversion.
Illustratively, referring to fig. 5, before the step S108, a step S107 is included:
step S107A, acquiring a key of the system account currently logged in by the user.
Specifically, the key of the user is taken to be decrypted according to the account ID of the system where the user logs in currently.
Step S107B, uploading the key to the target subsystem, so that the target subsystem uses the key as an encrypted salt, and encrypting the drawing data with the salt to obtain transmission data.
Specifically, data encryption is to encrypt the requested drawing data with the key as an encrypted salt value, such as: the interface API of the card configuration is (a1, a2, A3), a1, a2 are true entries, A3 is a signature (key), a1, a2 are configuration parameters, A3 encrypts a1 ═ XXX & a2 ═ XXX, and configuration data, i.e. transmission data, of A3 is obtained.
And step S110, receiving the drawing data returned by the target subsystem through the API, and drawing an interface according to the drawing data and the configuration data to obtain a display interface of the target subsystem.
Specifically, drawing data and data of an interface corresponding to the drawing development type are subjected to graphic drawing through an Echarts component, the drawing data are cut through the Echarts component according to the format of the interface, most of the left data are related to configuration data, and corresponding drawing data and setting data are required to be obtained for graphic drawing.
Exemplarily, referring to fig. 6, the step S110 includes:
step S110A, call the Echarts component to perform graphical drawing on the drawing data.
Specifically, the Echarts component draws the overall framework of the interface according to the drawing data, and can load a schedule module on the interface, add schedules, backlogs and the like by loading a calendar plug-in which vue plug-ins of the official website are used. And when there is an important event or an important date, whether to carry out message reminding is set on the calendar. Setting the level and the content of the important event on the data of the calendar plug-in, calling a message interface according to the level of the important event, and sending a content message to a user for the user to check.
Step S110B, interface-filling the drawn graphics with the configuration data to obtain a display interface of the target subsystem.
Specifically, the drawing data is filled into the drawn interface frame to obtain a display interface of the target subsystem. The interface can also be rendered through a rendering engine, so that the display interface is more flexible and vivid. The rendering engine may be implemented by a dynamic language (e.g., JavaScript language), i.e., the functions contained in the rendering engine are written by the dynamic language (e.g., JavaScript language). The rendering engine may be implemented in two parts, wherein one part is implemented in a natural language such as c/c + + for performance consideration and multithreading, and the other part is implemented in a dynamic language such as JavaScript. Of course, the rendering engine may be implemented entirely in a natural language such as c/c + +.
Example two
Referring to fig. 7, a schematic diagram of program modules of a second embodiment of the interface display system is shown. In the embodiment, the interface display system 20 may include or be divided into one or more program modules, and the one or more program modules are stored in a storage medium and executed by one or more processors to implement the interface display method. The program modules referred to in the embodiments of the present invention refer to a series of computer program instruction segments capable of performing specific functions, and are more suitable than the programs themselves for describing the execution process of the interface presentation system 20 in the storage medium. The following description will specifically describe the functions of the program modules of the present embodiment:
the receiving module 200 is configured to receive a target subsystem page loading instruction triggered by a user.
Specifically, a user selects a target subsystem on a main interface of a workbench, sets the target subsystem, and after the setting is completed, triggers a target subsystem page loading instruction, wherein the target subsystem page loading instruction is used for loading a set display page of the target subsystem, and the target subsystem page loading instruction comprises a system account and a password of the user.
A first obtaining module 202, configured to obtain a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, where the configuration file includes a development type, configuration data, and a loading address of the target subsystem.
Specifically, the configuration file is linked to according to a target subsystem page loading instruction, the configuration file is an xml file, the development type is an interface type, the loading address is an address of a corresponding card link, and the configuration data is data which needs to be displayed in the development type by a user.
A determining module 204, configured to determine whether the development type is an Iframe nested type or a non-Iframe nested type.
Specifically, whether the interface type is an Iframe nested type or not is judged, and whether a pre-drawn subsystem interface is called to a current main interface or not is indicated; if the prepared subsystem interface needs to be called, the subsystem interface is an Iframe nested type; if the prepared subsystem interface does not need to be called, the type is a non-Iframe nested type. If the type is a non-Iframe nested type, acquiring corresponding drawing data through an API (application programming interface), and drawing the drawing data according to the set data; if the type is an Iframe nested type, the graphical drawing is not needed, and only the user data is filled into the corresponding subsystem interface. When the original set page needs to be nested into the current page, Iframe nesting can be used, and there are two ways when Iframe nesting is used: 1) direct nesting of other websites does not need to be logged in; 2) acquiring the nested page only when other websites need to be logged in; the embodiment of the present invention employs the second method.
A second obtaining module 206, configured to, if the development type is an Iframe nested type, obtain a subsystem interface corresponding to the target subsystem according to the load address, and fill the configuration data in the subsystem interface to obtain a display interface of the target subsystem.
Specifically, if the development type is an Iframe nested type, a corresponding target subsystem interface is called. When the loading address is linked to the corresponding subsystem interface, the loading address passes through a system gateway of the subsystem interface, and the system gateway authenticates the loading address, wherein the authentication mode is SSO (Single sign on) authentication.
Illustratively, the second obtaining module 206 is further configured to:
and linking the subsystem gateway of the subsystem interface through the loading address.
Specifically, the loading address can be linked with a storage address of the subsystem interface, and the subsystem interface is acquired after passing through the subsystem gateway.
And receiving an authentication result of the subsystem gateway authenticating the loading address through single sign-on.
Specifically, the authentication result is whether the authentication load address can pass through the subsystem gateway of the corresponding target subsystem, and the single sign-on is a one-time authentication sign-on by the user. When the user logs in the identity authentication server once, the authority of accessing other associated systems and application software in the single sign-on system can be obtained, and meanwhile, the realization does not need an administrator to modify the login state or other information of the user, which means that in a plurality of application systems, the user can access all mutually trusted application systems only by logging in once. This approach reduces the time consumption resulting from logging in, assists with user management, and is currently popular. To implement the function of SSO, the application system must be able to identify the user who has logged in, by only logging in once. The application system can identify and extract tickets, and can automatically judge whether the current user logs in through communication with the authentication system, so that the single sign-on function is completed.
In addition:
(1) a single user information database is not necessary, many systems cannot store all user information in a centralized manner, and the user information should be allowed to be placed in different storages.
(2) The unified authentication system is not to say that only a single authentication server is provided
When the user accesses the application system 2, the authentication server 2 can recognize that the ticket is generated by the first server, and the function of SSO can still be achieved by exchanging authentication information through a standard communication protocol (for example, SAM L) between the authentication servers.
And if the authentication result is that the authentication is passed, acquiring a subsystem interface corresponding to the target subsystem.
Specifically, if the authentication is passed, calling a corresponding subsystem interface, and filling the configuration data into the corresponding subsystem interface to obtain a display interface of the subsystem; and if the SSO authentication is not passed, the corresponding subsystem interface is not called.
A third obtaining module 208, configured to obtain, if the development type is a non-Iframe nested type, an API interface corresponding to the target subsystem according to the load address.
Specifically, if the development type is a non-Iframe nested type, the API interface is called to obtain drawing data of the interface, and the load address may be linked to the corresponding API interface.
Illustratively, the third obtaining module 208 is further configured to:
and receiving the drawing data obtained by decrypting the transmission data through the API by the target subsystem.
Specifically, before the API interface is called, a key of the system account currently logged in by the user is acquired, and the key and the drawing data are encrypted to obtain transmission data. And when the API interface is called, acquiring the transmission data, transmitting the transmission data through the API interface, and judging whether the API interface can decrypt and verify the transmission data. When decrypting, the key is taken according to the account ID of the system which the user logs in at present, the transmitted data is decrypted, if the decryption is successful, the API interface is proved to be legal, the API interface can return the corresponding data, and if the decryption is failed, the illegal request is called. This ensures that the API interface is not accessed illegally. The safety of the API interface is ensured, and data leakage is prevented. If the API interface successfully decrypts the transmitted data, acquiring drawing data corresponding to the development type; if the API interface does not decrypt the transmitted data successfully, the page loading instruction of the subsystem is represented to be loaded illegally, and the API interface does not transmit the data.
Illustratively, the third obtaining module 208 is further configured to:
and acquiring the transmission format of the API.
Specifically, in the configuration file, the transmission format of the output parameter and the transmission format of the input parameter of the API interface are set, and the transmission format of the output parameter is obtained when data transmission is performed.
And receiving the drawing data transmitted by the target subsystem through the API according to the transmission format.
Specifically, the API interface returns the drawing data according to the transmission format of the callout on the configuration document without data conversion.
The drawing module 210 is configured to receive drawing data returned by the target subsystem through the API interface, and perform interface drawing according to the drawing data and the configuration data to obtain a display interface of the target subsystem.
Specifically, drawing data and data of an interface corresponding to the drawing development type are subjected to graphic drawing through an Echarts component, the drawing data are cut through the Echarts component according to the format of the interface, most of the left data are related to configuration data, and corresponding drawing data and setting data are required to be obtained for graphic drawing.
Illustratively, the rendering module 210 is further configured to:
and calling an Echarts component to perform graphical drawing on the drawing data.
Specifically, the Echarts component draws the overall framework of the interface according to the drawing data, and can load a schedule module on the interface, add schedules, backlogs and the like by loading a calendar plug-in which vue plug-ins of the official website are used. And when there is an important event or an important date, whether to carry out message reminding is set on the calendar. Setting the level and the content of the important event on the data of the calendar plug-in, calling a message interface according to the level of the important event, and sending a content message to a user for the user to check.
And performing interface filling on the drawn graph by the configuration data to obtain a display interface of the target subsystem.
Specifically, the drawing data is filled into the drawn interface frame to obtain a display interface of the target subsystem. The interface can also be rendered through a rendering engine, so that the display interface is more flexible and vivid. The rendering engine may be implemented by a dynamic language (e.g., JavaScript language), i.e., the functions contained in the rendering engine are written by the dynamic language (e.g., JavaScript language). The rendering engine may be implemented in two parts, wherein one part is implemented in a natural language such as c/c + + for performance consideration and multithreading, and the other part is implemented in a dynamic language such as JavaScript. Of course, the rendering engine may be implemented entirely in a natural language such as c/c + +.
EXAMPLE III
Fig. 8 is a schematic diagram of a hardware architecture of a computer device according to a third embodiment of the present invention. In the present embodiment, the computer device 2 is a device capable of automatically performing numerical calculation and/or information processing in accordance with a preset or stored instruction. The computer device 2 may be a rack server, a blade server, a tower server or a rack server (including an independent server or a server cluster composed of a plurality of servers), and the like. As shown in FIG. 8, the computer device 2 includes, but is not limited to, at least a memory 21, a processor 22, a network interface 23, and an interface presentation system 20, which are communicatively coupled to each other via a system bus. Wherein:
in this embodiment, the memory 21 includes at least one type of computer-readable storage medium including a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a Read Only Memory (ROM), an Electrically Erasable Programmable Read Only Memory (EEPROM), a Programmable Read Only Memory (PROM), a magnetic memory, a magnetic disk, an optical disk, and the like. In some embodiments, the storage 21 may be an internal storage unit of the computer device 2, such as a hard disk or a memory of the computer device 2. In other embodiments, the memory 21 may also be an external storage device of the computer device 2, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card), or the like provided on the computer device 2. Of course, the memory 21 may also comprise both internal and external memory units of the computer device 2. In this embodiment, the memory 21 is generally used for storing an operating system installed on the computer device 2 and various application software, such as the program codes of the interface display system 20 in the second embodiment. Further, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.
The network interface 23 may comprise a wireless network interface or a wired network interface, and the network interface 23 is generally used for establishing communication connection between the server 2 and other electronic devices. For example, the network interface 23 is used to connect the server 2 to an external terminal via a network, establish a data transmission channel and a communication connection between the server 2 and the external terminal, and the like. The network may be a wireless or wired network such as an Intranet (Intranet), the Internet (Internet), a Global System of Mobile communication (GSM), Wideband Code Division Multiple Access (WCDMA), a 4G network, a 5G network, Bluetooth (Bluetooth), Wi-Fi, and the like. It is noted that fig. 8 only shows the computer device 2 with components 20-23, but it is to be understood that not all shown components are required to be implemented, and that more or less components may be implemented instead.
In this embodiment, the interface display system 20 stored in the memory 21 can be further divided into one or more program modules, and the one or more program modules are stored in the memory 21 and executed by one or more processors (in this embodiment, the processor 22) to complete the present invention.
For example, fig. 7 is a schematic diagram of program modules for implementing the second embodiment of the interface display system 20, in which the interface display system 20 may be divided into a receiving module 200, a first obtaining module 202, a determining module 204, a second obtaining module 206, a third obtaining module 208, and a drawing module 210. The program module referred to in the present invention refers to a series of computer program instruction segments capable of performing specific functions, and is more suitable than a program for describing the execution process of the interface presentation system 20 in the computer device 2. The specific functions of the program modules 200 and 210 have been described in detail in the second embodiment, and are not described herein again.
Example four
The present embodiment also provides a computer-readable storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory (e.g., SD or DX memory, etc.), a Random Access Memory (RAM), a Static Random Access Memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, an optical disk, a server, an App application mall, etc., on which a computer program is stored, which when executed by a processor implements corresponding functions. The computer-readable storage medium of the embodiment is used for storing the interface display system 20, and when being executed by a processor, the interface display method of the first embodiment is implemented.
The above-mentioned serial numbers of the embodiments of the present invention are merely for description and do not represent the merits of the embodiments.
Through the above description of the embodiments, those skilled in the art will clearly understand that the method of the above embodiments can be implemented by software plus a necessary general hardware platform, and certainly can also be implemented by hardware, but in many cases, the former is a better implementation manner.
The above description is only a preferred embodiment of the present invention, and not intended to limit the scope of the present invention, and all modifications of equivalent structures and equivalent processes, which are made by using the contents of the present specification and the accompanying drawings, or directly or indirectly applied to other related technical fields, are included in the scope of the present invention.
Claims (10)
1. An interface display method, comprising:
receiving a target subsystem page loading instruction triggered by a user;
acquiring a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, wherein the configuration file comprises a development type, configuration data and a loading address of the target subsystem;
judging whether the development type is an Iframe nested type or a non-Iframe nested type;
if the development type is an Iframe nested type, acquiring a subsystem interface corresponding to the target subsystem according to the loading address, and filling the configuration data into the subsystem interface to obtain a display interface of the target subsystem;
if the development type is a non-Iframe nested type, acquiring an API (application programming interface) corresponding to the target subsystem according to the loading address;
and receiving the drawing data returned by the target subsystem through the API interface, and drawing an interface according to the drawing data and the configuration data to obtain a display interface of the target subsystem.
2. The interface display method of claim 1, wherein before receiving the user-triggered target subsystem page load instruction, the method comprises:
receiving a login instruction of the user;
acquiring a main interface of a workbench according to the login instruction, wherein the main interface of the workbench comprises a subsystem card list;
receiving a configuration instruction of a target subsystem card selected by the user in the subsystem card list;
and generating a configuration file corresponding to the target subsystem card according to the configuration instruction.
3. The interface display method according to claim 1, wherein the obtaining of the subsystem interface corresponding to the target subsystem according to the load address comprises:
a subsystem gateway linking the subsystem interface through the loading address;
receiving an authentication result of the subsystem gateway authenticating the loading address through single sign-on;
and if the authentication result is that the authentication is passed, acquiring a subsystem interface corresponding to the target subsystem.
4. The interface display method according to claim 1, wherein before the obtaining the API interface corresponding to the target subsystem according to the load address, the method includes:
acquiring a key of a system account currently logged in by the user;
and uploading the secret key to the target subsystem so that the target subsystem takes the secret key as an encrypted salt value, and encrypting the drawing data by adopting the salt value to obtain transmission data.
5. The interface exposure method of claim 4, wherein the receiving drawing data returned by the target subsystem through the API interface comprises:
and receiving the drawing data obtained by decrypting the transmission data through the API by the target subsystem.
6. The interface exposure method of claim 5, wherein the receiving drawing data returned by the target subsystem through the API interface comprises:
acquiring a transmission format of the API;
and receiving the drawing data transmitted by the target subsystem through the API according to the transmission format.
7. The interface display method according to claim 1, wherein the interface drawing according to the drawing data and the configuration data to obtain the display interface of the target subsystem comprises:
calling an Echarts component to carry out graphic drawing on the drawing data;
and performing interface filling on the drawn graph by the configuration data to obtain a display interface of the target subsystem.
8. An interface presentation system, comprising:
the receiving module is used for receiving a target subsystem page loading instruction triggered by a user;
the first acquisition module is used for acquiring a configuration file corresponding to the target subsystem according to the target subsystem page loading instruction, wherein the configuration file comprises the development type, the configuration data and the loading address of the target subsystem;
the judging module is used for judging whether the development type is an Iframe nested type or a non-Iframe nested type;
a second obtaining module, configured to, if the development type is an Iframe nested type, obtain a subsystem interface corresponding to the target subsystem according to the load address, and fill the configuration data in the subsystem interface to obtain a display interface of the target subsystem;
a third obtaining module, configured to obtain, if the development type is a non-Iframe nested type, an API interface corresponding to the target subsystem according to the load address;
and the drawing module is used for receiving the drawing data returned by the target subsystem through the API interface, and drawing an interface according to the drawing data and the configuration data to obtain a display interface of the target subsystem.
9. A computer arrangement, characterized in that the computer arrangement comprises a memory, a processor, the memory having stored thereon a computer program being executable on the processor, the computer program, when being executed by the processor, realizing the steps of the interface presentation method as claimed in any one of the claims 1-7.
10. A computer-readable storage medium, in which a computer program is stored which is executable by at least one processor for causing the at least one processor to carry out the steps of the interface presentation method according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010217522.2A CN111443958A (en) | 2020-03-25 | 2020-03-25 | Interface display method and system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010217522.2A CN111443958A (en) | 2020-03-25 | 2020-03-25 | Interface display method and system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN111443958A true CN111443958A (en) | 2020-07-24 |
Family
ID=71652453
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010217522.2A Pending CN111443958A (en) | 2020-03-25 | 2020-03-25 | Interface display method and system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111443958A (en) |
Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108469973A (en) * | 2017-02-20 | 2018-08-31 | 阿里巴巴集团控股有限公司 | Display methods, display device and the intelligent display device of interface content |
| CN110532495A (en) * | 2019-08-30 | 2019-12-03 | 郑州阿帕斯科技有限公司 | A kind of methods of exhibiting and device of webpage information |
-
2020
- 2020-03-25 CN CN202010217522.2A patent/CN111443958A/en active Pending
Patent Citations (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108469973A (en) * | 2017-02-20 | 2018-08-31 | 阿里巴巴集团控股有限公司 | Display methods, display device and the intelligent display device of interface content |
| CN110532495A (en) * | 2019-08-30 | 2019-12-03 | 郑州阿帕斯科技有限公司 | A kind of methods of exhibiting and device of webpage information |
Non-Patent Citations (2)
| Title |
|---|
| 佚名: "Echart示例", pages 1 - 7, Retrieved from the Internet <URL:https://www.cnblogs.com/john-xiong/p/12017981.html> * |
| 佚名: "iframe使用大全", pages 1 - 7, Retrieved from the Internet <URL:https://www.cnblogs.com/flicat/p/4441510.html> * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8117459B2 (en) | Personal identification information schemas | |
| EP2751950B1 (en) | Method for generating a soft token, computer program product and service computer system | |
| CA2632793A1 (en) | Information server and mobile delivery system and method | |
| CN110784450A (en) | Single sign-on method and device based on browser | |
| CN101588348A (en) | System logging method and system logging device based on Web | |
| CN104737175A (en) | Method and system for browser identity | |
| CN113079164B (en) | Remote control method and device for bastion machine resources, storage medium and terminal equipment | |
| US10375036B2 (en) | Content management system | |
| CN108038388B (en) | Method for realizing Web page seal, client and server | |
| CN112738004B (en) | Communication method and system based on QUIC transmission protocol | |
| US20100005476A1 (en) | Mobile electronic device including a portable application and a secured module able to communicate with each other, and associated communication method | |
| CN111343170A (en) | Electronic signing method and system | |
| CN114826733A (en) | File transfer method, device, system, apparatus, medium, and program product | |
| CN111339558A (en) | Data encryption method, data decryption method, computer device and medium | |
| US20200153828A1 (en) | Transparency mechanism for the local composition of personal user data stored in a distributed fashion | |
| CN112818270A (en) | Data cross-domain transfer method and device and computer equipment | |
| CN111882149B (en) | Budget declaration system | |
| CN111443958A (en) | Interface display method and system | |
| CN106712933A (en) | Identity authentication method and device based on mobile Internet terminal | |
| CN108259456B (en) | Method, device, equipment and computer storage medium for realizing user login-free | |
| CN102984142B (en) | The login system of enterprise resource planning and login method | |
| CN113064563A (en) | Printing method based on block chain | |
| WO2019062184A1 (en) | Bank insurance policy data interfacing method and insurance policy data server | |
| CN113645263B (en) | Account binding method and device | |
| CN113672993B (en) | Data processing method, system, equipment and computer readable storage medium |
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 | ||
| TA01 | Transfer of patent application right |
Effective date of registration: 20220601 Address after: 518000 China Aviation Center 2901, No. 1018, Huafu Road, Huahang community, Huaqiang North Street, Futian District, Shenzhen, Guangdong Province Applicant after: Shenzhen Ping An medical and Health Technology Service Co.,Ltd. Address before: Room 12G, Area H, 666 Beijing East Road, Huangpu District, Shanghai 200001 Applicant before: PING AN MEDICAL AND HEALTHCARE MANAGEMENT Co.,Ltd. |
|
| TA01 | Transfer of patent application right |