Data visualization system login method, device, equipment, medium and program product
By obtaining the authentication interface and obtaining the user login status in the target application system, and directly displaying the data visual page, the complex and costly single sign-in in the existing technology is solved, and a simplified single sign-in process is realized.
Patent Information
- Application Number
- CN202111486936.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-07
- Publication Date
- 2025-08-12
- Estimated Expiration
- 2041-12-07
AI Technical Summary
In the prior art, when single sign-in between multiple application systems and data visualization systems is implemented, the development method is complex and costly.
By obtaining the authentication interface in the target application system, obtaining the user's login status, and directly displaying the data visualization page in the display interface when the user is logged in, avoiding logging in again in the data visualization system.
A single sign-on between multiple application systems and data visualization systems is realized without creating a unified authentication system, reducing development complexity and cost.
Smart Images

Figure CN114239059B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of single sign-on technology, and in particular to a data visualization system login method, apparatus, device, medium, and program product. Background Art
[0002] Single Sign On (SSO) means that in multiple application systems, users only need to log in once to access all mutually trusted application systems.
[0003] In related technologies, many application systems have data visualization functions. To avoid duplication of development, existing data visualization system functions can be directly used to generate charts and dashboard pages. However, to ensure data security, data visualization systems generally have strict permission management, requiring users to log in and obtain authorization before viewing data. Based on this, a unified authentication system can be established between multiple application systems and data visualization systems. This authentication system verifies user identities and provides authentication credentials, allowing users to access the data visualization system without having to log in again.
[0004] However, in the related art, accessing the data visualization system through the authentication system has the problem of complex development method and high development cost. Summary of the Invention
[0005] Based on this, it is necessary to provide a data visualization system login method, device, equipment, medium and program product that can realize single sign-on between multiple application systems and data visualization systems at low cost to address the above technical problems.
[0006] In a first aspect, a data visualization system login method is provided, the method comprising:
[0007] In response to a data visualization request triggered by a user in a target application system, obtaining an authentication interface of the target application system; the data visualization request is used to request access to a data visualization page in the data visualization system through the target application system;
[0008] Obtain the user's login status in the target application system by calling the authentication interface;
[0009] If the user's login status in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system.
[0010] In one embodiment, the display interface of the target application system includes an access link to the data visualization page, and the data visualization request is sent after the user triggers the access link.
[0011] In one embodiment, the data visualization request includes an application identifier of a target application system;
[0012] Obtain the authentication interface of the target application system, including:
[0013] The authentication interface of the target application system is determined according to the data visualization request and the preset application configuration table; the application configuration table includes application identifiers of multiple application systems and corresponding authentication interfaces.
[0014] In one embodiment, the application configuration table also includes a preset whitelist of users;
[0015] Before obtaining the user's login status in the target application system by calling the authentication interface, the method further includes:
[0016] If the user belongs to the whitelist user, the data visualization page is displayed in the display interface of the target application system.
[0017] In one embodiment, the user's login status in the target application system is obtained by calling the authentication interface, including:
[0018] By calling the authentication interface, an authentication request is sent to the target application system. The authentication request is used to obtain the user's login status in the target application system;
[0019] Receive the authentication result sent by the target application system; the authentication result includes the user's login status in the target application system, whether logged in or not logged in.
[0020] In one embodiment, the method further comprises:
[0021] If the login status is not logged in, a login prompt message is sent to the user, and the login prompt message is used to prompt the user to perform a login operation in the target application system.
[0022] In one embodiment, the data visualization page is used to provide a variety of visualization charts, visualization relationship diagrams, and visualization dashboards;
[0023] Visual chart types include at least one of detailed tables, indicator cards, bar charts, pie charts, line charts, rectangular tree charts, and funnel charts; visual relationship diagrams include at least one of tree charts, dashboards, four-quadrant charts, and mind maps; and visual dashboards are the layout of visual charts and visual relationship diagrams.
[0024] In a second aspect, a data visualization system login device is provided, the device comprising:
[0025] A first acquisition module is configured to acquire an authentication interface of the target application system in response to a data visualization request triggered by a user in the target application system; the data visualization request is configured to request access to a data visualization page in the data visualization system through the target application system;
[0026] The second acquisition module is used to obtain the user's login status in the target application system by calling the authentication interface;
[0027] The display module is used to display the data visualization page in the display interface of the target application system if the user's login status in the target application system is logged in.
[0028] In a third aspect, a single sign-on system is provided, the system comprising at least one target application system and a data visualization system;
[0029] The target application system is used to send user-triggered data visualization requests to the data visualization system;
[0030] The data visualization system is used to obtain the authentication interface of the target application system, and obtain the user's login status in the target application system by calling the authentication interface. If the user's login status in the target application system is logged in, the data visualization page is displayed in the interface of the target application system.
[0031] In a fourth aspect, a computer device is provided, comprising a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the steps of the method provided in any one of the embodiments of the first aspect are implemented.
[0032] In a fifth aspect, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps of the method provided in any embodiment of the first aspect are implemented.
[0033] In a sixth aspect, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the steps of the method provided in any one of the embodiments of the first aspect.
[0034] The above-mentioned data visualization system login method, apparatus, equipment, medium and program product obtain the authentication interface of the target application system in response to the data visualization request triggered by the user in the target application system; obtain the user's login status in the target application system by calling the authentication interface; if the user's login status in the target application system is logged in, display the data visualization page in the display interface of the target application system. Among them, the data visualization request is used to request access to the data visualization page in the data visualization system through the target application system. In this application, the user's login status in the target application system is obtained through the authentication interface of the application system, and then, if the user's login status in the target application system is logged in, the data visualization page can be accessed without logging in again in the data visualization system. In this way, single sign-on is achieved between the target application system and the data visualization system through the authentication interface, without the need to create a unified authentication system, thereby reducing development complexity and development costs. BRIEF DESCRIPTION OF THE DRAWINGS
[0035] Figure 1 This is an application environment diagram of a data visualization system login method in one embodiment;
[0036] Figure 2 Schematic diagram of a data visualization system login method in one embodiment;
[0037] Figure 3 A flowchart of a data visualization system login method in another embodiment;
[0038] Figure 4 A flowchart of a data visualization system login method in another embodiment;
[0039] Figure 5 is a schematic diagram of a single sign-on system in one embodiment;
[0040] Figure 6 It is a structural block diagram of a data visualization system login device in one embodiment;
[0041] Figure 7 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION
[0042] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.
[0043] The data visualization system login method provided in the embodiment of the present application can be applied to Figure 1In the application environment shown, the server in the application environment can be an independent server for deploying the data visualization system, or a server composed of multiple servers.
[0044] Among them, the internal structure of the server is as follows Figure 1 As shown, the processor in this internal structure is used to create an application configuration table and generate a data visualization page. The memory in this internal structure includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database is used to store relevant data for each application system. The network interface is used to communicate with an external terminal via a network connection. When executed by the processor, the computer program implements a data visualization system login method.
[0045] When executing the data visualization system login method provided in the embodiment of the present application, the server of the data visualization system communicates with at least one application system through an authentication interface, so that when a user requests a data visualization page, the server obtains the user's login status in the application system by calling the authentication interface of the application system.
[0046] In the related art, when single sign-on is implemented between multiple application systems and data visualization systems, it is necessary to establish a unified authentication system between the multiple application systems and data visualization systems in advance. When a user accesses the application system for the first time, because he has not logged in yet, he will be directed to the authentication system to log in. The authentication system performs identity verification based on the login information provided by the user, and if the verification is passed, it returns an authentication credential (ticket) to the user. When the user accesses the data visualization system, the ticket is carried in the access request as his own authentication credential. After the data visualization system receives the access request sent by the user, it sends the ticket carried in the access request to the authentication system for verification, and the authentication system checks the legitimacy of the ticket. If the authentication system checks that the ticket is legal, the user can access the data visualization system without logging in again.
[0047] However, building a unified authentication system and transforming existing application systems and data visualization systems according to the unified authentication system to form an authentication system will make the development method more complicated and the development cost higher.
[0048] Based on this, embodiments of the present application provide a data visualization system login method, apparatus, device, medium, and program product that enable single sign-on between multiple application systems and the data visualization system without adding a unified authentication system. That is, after a user enters login information in an application system and passes identity verification, they can access the data visualization page directly when accessing the data visualization system without having to enter login information again.
[0049] The following will explain in detail the technical solutions of the embodiments of the present application and how the technical solutions of the embodiments of the present application solve the above-mentioned technical problems through examples and in combination with the accompanying drawings. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be repeated in some embodiments. It should be noted that the embodiment of the present application provides a data visualization system login method, and its execution subject can be the background server of the data visualization system, or it can be a data visualization system login device, which can be implemented as part or all of the processor through software, hardware, or a combination of software and hardware. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments.
[0050] In one embodiment, Figure 2 As shown, a data visualization system login method is provided, which is applied to Figure 1 The following steps are used as an example to illustrate the server in the example:
[0051] Step 210: In response to a data visualization request triggered by a user in a target application system, an authentication interface of the target application system is obtained.
[0052] The data visualization request is used to request access to a data visualization page in the data visualization system through the target application system.
[0053] It should be noted that many application systems have functions related to data visualization. In order to avoid duplication of development, the existing data visualization system functions can be directly used to generate charts and dashboard pages. That is, in the embodiment of the present application, the application system is integrated with the data visualization function.
[0054] Furthermore, an access interface or access link of the data visualization system is pre-set in the target application system. Then, after the user views the business services provided by the target application in the target application system, he can access the data visualization system to visualize the corresponding data and obtain a visualization chart.
[0055] The target application system is integrated with a data visualization function, and its display interface includes an access link to a data visualization page. The data visualization request is sent after the user triggers the access link.
[0056] In one possible implementation, step 210 may be implemented as follows: after a user triggers an access link to a data visualization page in a target application system, the target application system sends a data visualization request to the data visualization system. After receiving the data visualization request, the data visualization system obtains an authentication interface of the target application system.
[0057] Among them, the authentication interface of the target application system is set in the background server of the target application system, which is used for the data visualization system to mobilize and authenticate users who access the data visualization system.
[0058] As an example, the authentication interface may be a Uniform Resource Locator (URL) of the target application system.
[0059] Step 220: Obtain the user's login status in the target application system by calling the authentication interface.
[0060] The target application system serves as a unified portal, and users access the data visualization system through an access link within the target application system. Therefore, to assist the data visualization system in performing single-sign-on authentication for accessing users, the target application system stores the user's user information, login information, and login status after the user logs into the application system.
[0061] Optionally, the target application system is pre-set with a login information collection interval. The target application system confirms the user's login status according to the collection interval and updates the stored user login status in time to ensure that the user's login status is real-time and effective, thereby improving authentication accuracy.
[0062] In one possible implementation, after a user logs in to a target application system, the target application system sends the user's login status to the data visualization system. As the user's login time progresses, the target application system updates the user's login status at a collection interval and sends the updated user login status to the data visualization system. The data visualization system caches the user login status sent by the target application system according to the target application system's corresponding authentication interface.
[0063] When the data visualization system receives a data visualization request, it queries the user's latest login status from the cache according to the authentication interface of the target application system.
[0064] In another possible implementation, after receiving the data visualization request, the data visualization system calls the authentication interface to obtain the user's login status from the target application system in real time.
[0065] The user's login status includes logged in or not logged in. If the user's login status is logged in, it means that the user has entered login information into the target application system, and the target application system has verified the legitimacy of the user's identity. If the user's login status is not logged in, it means that the user has not entered login information into the target application system, or the login information entered by the user has failed verification and the legitimacy of their identity has not been verified.
[0066] Step 230: If the user's login status in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system.
[0067] Among them, the target application system and the data visualization system are mutually trusted systems. When the user has logged in to the target application system, that is, after the target application system has verified the legitimacy of the user's identity, the data visualization system no longer needs to perform secondary verification and can directly display the data visualization page to the user.
[0068] It's important to note that data visualization systems come pre-configured with data visualization pages, including charts, relationship diagrams, and dashboards, and are configured with the relevant permissions for the application systems to be connected. Furthermore, data visualization systems generally feature comprehensive data visualization page generation capabilities and fine-grained permission management.
[0069] In a possible implementation, the data visualization page is used to provide a variety of visualization charts, visualization relationship diagrams, and visualization dashboards.
[0070] Among them, the visual chart includes at least one of a detailed list, an indicator card, a bar chart, a pie chart, a line chart, a rectangular tree chart, and a funnel chart; the visual relationship diagram includes at least one of a tree chart, a dashboard, a four-quadrant diagram, and a mind map; the visual dashboard is the layout method of the visual chart and the visual relationship diagram.
[0071] As an example, after displaying a data visualization page to a user, the user can use the visualization charts and / or visualization relationship diagrams on the data visualization page to visualize the business data obtained from the target application system to obtain visualized data. Furthermore, the processed visualized data can be displayed using a visualization dashboard provided on the data visualization page in a corresponding layout.
[0072] In the above-mentioned data visualization system login method, the data visualization system responds to the data visualization request triggered by the user in the target application system, obtains the authentication interface of the target application system; by calling the authentication interface, obtains the login status of the user in the target application system; if the login status of the user in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system. That is, the embodiment of the present application obtains the login status of the user in the target application system through the authentication interface of the application system, and then, if the login status of the user in the target application system is logged in, the data visualization page can be accessed without logging in again in the data visualization system. In this way, single sign-on is realized between the target application system and the data visualization system through the authentication interface, without the need to create a unified authentication system, thereby reducing development complexity and development costs.
[0073] Regarding the data system obtaining the authentication interface of the target application system in the previous embodiment, this is described in detail through an embodiment below.
[0074] In one embodiment, the data visualization request in the above step 210 includes the application identifier of the target application system, and the implementation process of the data visualization system obtaining the authentication interface of the target application system can be: determining the authentication interface of the target application system according to the data visualization request and the preset application configuration table, and the application configuration table includes the application identifiers of multiple application systems and the corresponding authentication interfaces.
[0075] It should be noted that the application configuration table can be that the application system sets the access link of the data visualization page in its own display interface, and then sends its own application identification and authentication interface to the data visualization system so that the data visualization system can establish the application configuration table.
[0076] The authentication interface and application identifier of the application system are unique. That is, the data visualization system can determine a unique authentication interface based on the application identifier, or determine a unique application system based on the authentication interface.
[0077] Optionally, the application configuration table may also include other application information such as the application name of each application system, which is not limited in this embodiment of the present application.
[0078] Optionally, the application configuration table may also include preset whitelist users, so that the data visualization system can adopt different response methods to data visualization requests triggered by non-whitelist users and whitelist users to improve user experience.
[0079] As an example, Table 1 below provides an application configuration table. The application identifier can be the application system's own identifier, or a string randomly generated by the data visualization system to distinguish each application system from other applications. The authentication interface is the unique access address for each application system's information resources.
[0080] Table 1
[0081] Application Name Application Identification Authentication interface (URL) Whitelist users Application System 1 Zgxih8ki https: / / ip1 / auth User A Application System 2 JsPNmb8z https: / / ip2 / auth User B
[0082] Referring to Table 1, the application configuration table uses application system 1 and application system 2 as examples for description, and only user A and user B are used as examples of whitelisted users. It should be understood that the application configuration table may also include other application systems, and the whitelisted users of each application system may be multiple users, and this embodiment of the application does not limit this.
[0083] In this embodiment, the data visualization system pre-creates an application configuration table based on the application system to be connected. This allows the system to quickly and accurately determine the target application system's authentication interface based on the application configuration table upon receiving a data visualization request, and then proceed with the authentication process.
[0084] Based on the application configuration table in the above embodiment, the embodiment of the present application provides different response methods for data visualization requests triggered by whitelist users and non-whitelist users.
[0085] In a data visualization system login scenario, for whitelisted users, there is no need to call the authentication interface to obtain the user's login status in the target application system. In other words, if the user is a whitelisted user, the data visualization page is displayed in the display interface of the target application system.
[0086] Whitelisted users can be administrators, staff, or important users of each application system. The target application system fully trusts the identity of whitelisted users. Therefore, after a whitelisted user logs in once, they can directly access the target application system and data visualization system without having to verify the legitimacy of their login information and identity again.
[0087] Therefore, in this scenario, the data visualization request triggered by the user in the target application system includes the application identifier of the target application system and the user identifier.
[0088] In one possible implementation, the data visualization system responds to a data visualization request triggered by a user in a target application system by obtaining the target application system's corresponding application identifier and the user identifier from the data visualization request. Based on the application identifier, the system then queries the target application system's whitelist of users in the application configuration table to determine whether the user identified by the user identifier is a whitelisted user. If the user is a whitelisted user, a jump link to the data visualization page is directly returned to the target application system. The target application system then jumps to the data visualization page via the jump link, displaying the data visualization page to the user.
[0089] In this way, for whitelist users, the target application system and data visualization system only need to verify the legitimacy of the login information and identity once, that is, provide corresponding data visualization services to whitelist users, thereby increasing the rate at which whitelist users access the data visualization system and providing a better user experience.
[0090] In another data visualization system login scenario, for non-whitelisted users, such as Figure 3 As shown, the implementation process of the data visualization system in step 220 obtaining the user's login status in the target application system through the authentication interface may include the following steps:
[0091] Step 310: Send an authentication request to the target application system by calling the authentication interface. The authentication request is used to obtain the user's login status in the target application system.
[0092] In this step, the data visualization system uses the target application system's application identifier to query the application configuration table, determine the target application system's authentication interface, and then send an authentication request to the target application system through the authentication interface.
[0093] The authentication request carries the user's user identification, so that the target application system can determine the unique user according to the user identification.
[0094] Furthermore, after receiving the authentication request from the data visualization system, the target application system obtains the user ID from the authentication request. Then, based on the user ID, it identifies the target user, queries the target user's login status, and sends the target user's login status as the authentication result to the data visualization system.
[0095] Step 320: Receive the authentication result sent by the target application system; the authentication result includes the user's login status in the target application system, whether logged in or not logged in.
[0096] In this step, after receiving the authentication result, the data visualization system determines whether it is necessary to verify the user's login information and identity legitimacy again based on the user's login status.
[0097] If the user's login status in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system; if the user's login status in the target application system is not logged in, a login prompt message is sent to the user, and the login prompt message is used to prompt the user to log in to the target application system.
[0098] In other words, only after logging in to the target application system can the user access the data visualization system without entering login information and directly access the data visualization page. If the user is not logged in to the target application system, they must log in to the target application system first.
[0099] Furthermore, after the data visualization system sends a login prompt message to the user, the target application system can pre-set the display time of the login prompt message. After the display time expires, it automatically jumps to the login page for the user to enter the login information and complete the login in the target application system.
[0100] In this embodiment, when a user triggers a data visualization request in the target application system, the data visualization system determines whether the user is a whitelist user based on the application identifier of the target application system and the user identifier of the user carried in the data visualization request. If the user is a whitelist user, the data visualization page is sent directly; if the user is not a whitelist user, the user's login status in the target application system is further obtained. If the user's login status in the target application system is logged in, the data visualization page is sent directly; if the user's login status in the target application system is not logged in, the user is prompted to log in in the target application system first. In this way, through the authentication interface set by the target application system, the data visualization system can obtain the user's login status in the target application system to achieve single sign-on between the target application system and the data visualization system.
[0101] In addition, in one embodiment, the present application also provides another data visualization system login method, which is applied to Figure 1 The server in the example is as follows: Figure 4 As shown, the process includes the following steps:
[0102] Step 402: In response to the user triggering an access link of a data visualization page in the display interface, the target application system sends a data visualization request to the data visualization system.
[0103] The data visualization request includes an application identifier of the target application.
[0104] Step 404: The data visualization system receives a data visualization request.
[0105] Step 406: The data visualization system determines whether the user is a whitelist user based on the data visualization request and a preset application configuration table.
[0106] The application configuration table includes application identifiers of multiple application systems, corresponding authentication interfaces, and corresponding whitelist users.
[0107] Step 408: If the user is a whitelisted user, the data visualization system sends a data visualization page to the target application system.
[0108] Step 410: The target application system displays a data visualization page in the display interface.
[0109] Step 412: If the user does not belong to the whitelisted users, the data visualization system determines the authentication interface of the target application system according to the data visualization request and the preset application configuration table.
[0110] Step 414: The data visualization system sends an authentication request to the target application system by calling the authentication interface.
[0111] The authentication request is used to obtain the user's login status in the target application system.
[0112] Step 416: The target application system receives the authentication request and determines the user's login status in the target application system.
[0113] Step 418: The target application system sends the user's login status as the authentication result to the data visualization system.
[0114] The authentication result includes whether the user's login status in the target application system is logged in or not logged in.
[0115] Step 420: The data visualization system receives the authentication result sent by the target application system.
[0116] Step 422: If the user's login status in the target application system is logged in, the data visualization system sends a data visualization page to the target application system.
[0117] Step 424: The target application system displays the data visualization page in the display interface.
[0118] Step 426: If the user's login status in the target application system is not logged in, the data visualization system sends a login prompt message to the user sent by the target application system.
[0119] The login prompt information is used to prompt the user to perform a login operation in the target application system.
[0120] The implementation principles and technical effects of each step in the data visualization system login method provided in this embodiment are similar to those in the previous method embodiments and will not be repeated here.
[0121] It should be understood that, although the various steps in the flowcharts of the above-described embodiments are shown in sequence as indicated by the arrows, these steps are not necessarily performed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps may be performed in other orders. Moreover, at least a portion of the steps in the flowcharts of the above-described embodiments may include multiple steps or multiple stages, and these steps or stages are not necessarily performed at the same time, but may be performed at different times, and the execution order of these steps or stages is not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least a portion of steps or stages in other steps.
[0122] In one embodiment, Figure 5 As shown, the embodiment of the present application further provides a single sign-on system 500, which includes at least one target application system 510 and a data visualization system 520;
[0123] The target application system 510 is configured to send a user-triggered data visualization request to the data visualization system;
[0124] The data visualization system 520 is used to obtain the authentication interface of the target application system, and obtain the user's login status in the target application system by calling the authentication interface. If the user's login status in the target application system is logged in, the data visualization page is displayed in the interface of the target application system.
[0125] Among them, an access link to the data visualization page is set in the display interface of the target application system, and the data visualization system can execute any step of the data visualization system login method provided in the embodiment of the present application.
[0126] It should be noted that the data visualization system executes the steps in any of the above method embodiments, and its implementation principles and technical effects are similar to those in the previous method embodiments, which will not be repeated here.
[0127] In one embodiment, Figure 6 As shown, the embodiment of the present application further provides a data visualization system login device, the device 600 including: a first acquisition module 610, a second acquisition module 620 and a display module 630, wherein:
[0128] A first acquisition module 610 is configured to acquire an authentication interface of the target application system in response to a data visualization request triggered by a user in the target application system; the data visualization request is configured to request access to a data visualization page in the data visualization system through the target application system;
[0129] The second acquisition module 620 is used to obtain the user's login status in the target application system by calling the authentication interface;
[0130] The display module 630 is configured to display a data visualization page in a display interface of the target application system if the user's login status in the target application system is logged in.
[0131] In one embodiment, the display interface of the target application system includes an access link to the data visualization page, and the data visualization request is sent after the user triggers the access link.
[0132] In one embodiment, the data visualization request includes an application identifier of a target application system;
[0133] The first acquisition module 610 includes:
[0134] The determination unit is used to determine the authentication interface of the target application system according to the data visualization request and a preset application configuration table; the application configuration table includes application identifiers of multiple application systems and corresponding authentication interfaces.
[0135] In one embodiment, the application configuration table also includes a preset whitelist of users;
[0136] The display module 630 is further configured to:
[0137] If the user belongs to the whitelist user, the data visualization page is displayed in the display interface of the target application system.
[0138] In one embodiment, the second acquisition module 620 includes:
[0139] The sending unit is used to send an authentication request to the target application system by calling the authentication interface, and the authentication request is used to obtain the user's login status in the target application system;
[0140] The receiving unit is used to receive the authentication result sent by the target application system; the authentication result includes the login status of the user in the target application system, namely logged in or not logged in.
[0141] In one embodiment, the apparatus further comprises:
[0142] The sending module is used to send a login prompt message to the user if the login status is not logged in. The login prompt message is used to prompt the user to perform a login operation in the target application system.
[0143] In one embodiment, the data visualization page is used to provide a variety of visualization charts, visualization relationship diagrams, and visualization dashboards;
[0144] Visual chart types include at least one of detailed tables, indicator cards, bar charts, pie charts, line charts, rectangular tree charts, and funnel charts; visual relationship diagrams include at least one of tree charts, dashboards, four-quadrant charts, and mind maps; and visual dashboards are the layout of visual charts and visual relationship diagrams.
[0145] The specific definition of the data visualization system login device can be found in the definition of the data visualization system login method above, and will not be repeated here. The various modules in the above-mentioned data visualization system login device can be implemented in whole or in part through software, hardware, or a combination thereof. The above-mentioned modules can be embedded in or independent of the processor in the computer device in hardware form, or can be stored in the memory of the computer device in software form, so that the processor can call and execute the corresponding operations of the above-mentioned modules.
[0146] In one embodiment, the present application also provides a computer device, the internal structure of which can be as follows: Figure 7 As shown. The computer device includes a processor, a memory, a communication interface, a display screen and an input device connected via a system bus. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner, and the wireless manner can be achieved through WIFI, an operator network, NFC (near field communication) or other technologies. When the computer program is executed by the processor, a data visualization system login method is implemented. The display screen of the computer device can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer device can be a touch layer covering the display screen, or a button, trackball or touchpad provided on the computer device housing, or an external keyboard, touchpad or mouse.
[0147] Those skilled in the art will understand that Figure 7 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.
[0148] In one embodiment, the present application further provides a computer device, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:
[0149] In response to a data visualization request triggered by a user in a target application system, obtaining an authentication interface of the target application system; the data visualization request is used to request access to a data visualization page in the data visualization system through the target application system;
[0150] Obtain the user's login status in the target application system by calling the authentication interface;
[0151] If the user's login status in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system.
[0152] When the computer device provided in this embodiment implements the above steps, its implementation principle and technical effects are similar to those of the above method embodiment, and will not be repeated here.
[0153] In one embodiment, the present application further provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the following steps are implemented:
[0154] In response to a data visualization request triggered by a user in a target application system, obtaining an authentication interface of the target application system; the data visualization request is used to request access to a data visualization page in the data visualization system through the target application system;
[0155] Obtain the user's login status in the target application system by calling the authentication interface;
[0156] If the user's login status in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system.
[0157] When the computer-readable storage medium provided in this embodiment implements the above steps, its implementation principle and technical effects are similar to those of the above method embodiment, and will not be repeated here.
[0158] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:
[0159] In response to a data visualization request triggered by a user in a target application system, obtaining an authentication interface of the target application system; the data visualization request is used to request access to a data visualization page in the data visualization system through the target application system;
[0160] Obtain the user's login status in the target application system by calling the authentication interface;
[0161] If the user's login status in the target application system is logged in, the data visualization page is displayed in the display interface of the target application system.
[0162] When the computer program product provided in this embodiment implements the above steps, its implementation principle and technical effects are similar to those of the above method embodiment, and will not be repeated here.
[0163] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory or optical memory, etc. Volatile memory may include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM).
[0164] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0165] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present invention. It should be noted that a person skilled in the art could make various modifications and improvements without departing from the spirit of the present application, all of which fall within the scope of protection of the present application. Therefore, the scope of protection of the present patent application shall be determined by the appended claims.
Claims
1. A data visualization system login method, characterized in that: The method comprises: In response to a data visualization request triggered by a user in a target application system, obtaining an authentication interface of the target application system; the data visualization request is used to request access to a data visualization page in the data visualization system through the target application system; the data visualization request is triggered by the user in the target application system by triggering an access link and / or an access interface of the data visualization page; the data visualization request includes an application identifier of the target application system; Obtaining the login status of the user in the target application system by calling the authentication interface; If the user's login status in the target application system is logged in, displaying the data visualization page in the display interface of the target application system; The obtaining of the authentication interface of the target application system includes: The authentication interface of the target application system is determined according to the data visualization request and a preset application configuration table; the application configuration table includes application identifiers of multiple application systems and corresponding authentication interfaces.
2. The method according to claim 1, characterized in that The display interface of the target application system includes an access link to the data visualization page, and the data visualization request is sent after the user triggers the access link.
3. The method according to claim 1, characterized in that The application configuration table also includes preset whitelist users; Before acquiring the login status of the user in the target application system by calling the authentication interface, the method further includes: If the user belongs to the whitelisted users, a data visualization page is displayed in the display interface of the target application system.
4. The method according to any one of claims 1 to 2, characterized in that The step of obtaining the user's login status in the target application system by calling the authentication interface includes: By calling the authentication interface, sending an authentication request to the target application system, the authentication request is used to obtain the login status of the user in the target application system; Receive the authentication result sent by the target application system; the authentication result includes the login status of the user in the target application system, namely logged in or not logged in.
5. The method according to claim 4, characterized in that The method further comprises: If the login status is not logged in, a login prompt message is sent to the user, where the login prompt message is used to prompt the user to perform a login operation in the target application system.
6. The method according to any one of claims 1-2, characterized in that The data visualization page is used to provide a variety of visualization charts, visualization relationship diagrams and visualization dashboards; The visual chart includes at least one of a detailed list, an indicator card, a bar chart, a pie chart, a line chart, a rectangular tree chart, and a funnel chart; the visual relationship diagram includes at least one of a tree chart, a dashboard, a four-quadrant diagram, and a mind map; the visual dashboard is a layout method of the visual chart and the visual relationship diagram.
7. A data visualization system login device, characterized in that: The device comprises: A first acquisition module is configured to acquire an authentication interface of a target application system in response to a data visualization request triggered by a user in a target application system; the data visualization request is used to request access to a data visualization page in the data visualization system through the target application system; the data visualization request is triggered by the user in the target application system by triggering an access link and / or an access interface of the data visualization page; the data visualization request includes an application identifier of the target application system; A second acquisition module is used to obtain the login status of the user in the target application system by calling the authentication interface; A display module, configured to display the data visualization page on a display interface of the target application system if the login status of the user in the target application system is logged in; The obtaining of the authentication interface of the target application system includes: The authentication interface of the target application system is determined according to the data visualization request and a preset application configuration table; the application configuration table includes application identifiers of multiple application systems and corresponding authentication interfaces.
8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.
Citation Information
Patent Citations
Page login authentication method and related device
CN111177612A
User login processing method and device and electronic equipment
CN113422752A