CN112464259A - ERP page acquisition method and device, computer equipment and storage medium - Google Patents
ERP page acquisition method and device, computer equipment and storage medium Download PDFInfo
- Publication number
- CN112464259A CN112464259A CN202011293221.4A CN202011293221A CN112464259A CN 112464259 A CN112464259 A CN 112464259A CN 202011293221 A CN202011293221 A CN 202011293221A CN 112464259 A CN112464259 A CN 112464259A
- Authority
- CN
- China
- Prior art keywords
- page
- application
- erp
- authentication information
- middleware
- 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.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 44
- 238000004590 computer program Methods 0.000 claims description 24
- 238000004891 communication Methods 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000005516 engineering process Methods 0.000 description 4
- 230000008569 process Effects 0.000 description 4
- 102100037245 EP300-interacting inhibitor of differentiation 2 Human genes 0.000 description 3
- 101000881675 Homo sapiens EP300-interacting inhibitor of differentiation 2 Proteins 0.000 description 3
- 230000006870 function Effects 0.000 description 3
- 230000009191 jumping Effects 0.000 description 3
- 238000007726 management method Methods 0.000 description 3
- 238000013507 mapping Methods 0.000 description 3
- 230000005540 biological transmission Effects 0.000 description 2
- 238000011161 development Methods 0.000 description 2
- 230000009471 action Effects 0.000 description 1
- 238000004458 analytical method Methods 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 230000010365 information processing Effects 0.000 description 1
- 239000004973 liquid crystal related substance Substances 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 238000012795 verification Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Classifications
-
- 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/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/955—Retrieval from the web using information identifiers, e.g. uniform resource locators [URL]
-
- 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/60—Protecting data
- G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures
-
- 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/46—Multiprogramming arrangements
- G06F9/54—Interprogram communication
- G06F9/546—Message passing systems or structures, e.g. queues
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F2209/00—Indexing scheme relating to G06F9/00
- G06F2209/54—Indexing scheme relating to G06F9/54
- G06F2209/547—Messaging middleware
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computer Security & Cryptography (AREA)
- General Health & Medical Sciences (AREA)
- Computer Hardware Design (AREA)
- Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Information Transfer Between Computers (AREA)
Abstract
The application relates to an ERP page acquisition method, an ERP page acquisition device, computer equipment and a storage medium. The method comprises the following steps: when receiving an operation of opening an application page corresponding to a target application, acquiring application authentication information corresponding to the target application and page authentication information of the application page; acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information; determining an ERP service address corresponding to the application page according to the first page identity identification information; and performing page access according to the ERP service address to obtain and display the application page. By adopting the method, the access efficiency of the ERP page can be improved.
Description
Technical Field
The present application relates to the field of information processing technologies, and in particular, to a method and an apparatus for obtaining an ERP page, a computer device, and a storage medium.
Background
An ERP (enterprise Resource planning) system, abbreviated as ERP, is an abbreviated form of integrated management information system, and is a management platform provided with a systematized management idea on the basis of information technology. With the development of communication technology and the requirement of enterprise diversified business, the application of the ERP is more and more extensive, and a user wants to be able to stably acquire an ERP page in real time when accessing the ERP.
However, the access address of the application page can be displayed in the application, the access address of the page is fixed in the application, and there are cases that the corresponding ERP page cannot be accessed according to the page address, which results in low page access efficiency.
Disclosure of Invention
Therefore, it is necessary to provide an ERP page obtaining method, an apparatus, a computer device and a storage medium, which can improve stability of obtaining an ERP page, in view of the above technical problems.
An ERP page acquisition method, the method comprising:
when receiving an operation of opening an application page corresponding to a target application, acquiring application authentication information corresponding to the target application and page authentication information of the application page;
acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information;
determining an ERP service address corresponding to the application page according to the first page identity identification information;
and performing page access according to the ERP service address to obtain and display the application page.
In one embodiment, the determining, according to the first page identification information, an ERP service address corresponding to the application page includes:
acquiring a first network electronic identifier of the application page on the middleware according to the first page identity identification information;
determining middleware authentication information of the middleware according to the first network electronic identifier and a first ERP platform identifier corresponding to the application page;
sending the middleware authentication information to an ERP server corresponding to the first ERP platform identification, so that the ERP server obtains corresponding second page identity identification information according to the middleware authentication information;
and matching the first page identification information with the second page identification information, and acquiring the ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
In one embodiment, the method further comprises the following steps: when the ERP service addresses are not matched, displaying an ERP service address setting page corresponding to the application page;
and acquiring the binding relationship between the first page identity identification information and the ERP service address through the service address setting page.
In one embodiment, the sending the middleware authentication information to the ERP server corresponding to the first ERP platform identifier includes:
receiving an encrypted public key corresponding to the ERP server;
encrypting the middleware authentication information by using the encryption public key to form encrypted middleware authentication information;
adding a signature to the encrypted middleware authentication information by using a local private key to obtain signed middleware authentication information;
and sending the signed middleware authentication information to the ERP server.
In one embodiment, the obtaining of the application authentication information corresponding to the target application includes:
acquiring an application identifier of the application page and a page key of the application page;
and acquiring application authentication information corresponding to the target application according to the page identifier and the page key.
In one embodiment, the method further comprises the following steps: when a push message of an ERP push server is received, acquiring a second ERP platform identifier corresponding to the ERP push server, a push page identifier corresponding to a push message display page and a second network electronic identifier corresponding to the push message display page;
determining a message pushing interface according to the second ERP platform identification, the pushing page identification and the second network electronic identification;
and pushing the push message to the push message display page through the message pushing interface.
An ERP page obtaining apparatus, the apparatus comprising:
the application authentication information and page authentication information acquisition module is used for acquiring application authentication information corresponding to a target application and page authentication information of the application page when receiving an operation of opening the application page corresponding to the target application;
the first page identity information acquisition module is used for acquiring first page identity information corresponding to the application page according to the application authentication information and the page authentication information;
the ERP service address acquisition module is used for determining an ERP service address corresponding to the application page according to the first page identity identification information;
and the application page acquisition and display module is used for carrying out page access according to the ERP service address so as to acquire and display the application page.
In one embodiment, the ERP service address obtaining module includes:
the first network electronic identification acquisition unit is used for acquiring a first network electronic identification of the application page on the middleware according to the first page identity identification information;
the middleware authentication information determining unit is used for determining the middleware authentication information of the middleware according to the first network electronic identifier and the first ERP platform identifier corresponding to the application page;
the middleware authentication information sending unit is used for sending the middleware authentication information to an ERP server corresponding to the first ERP platform identifier so that the ERP server can obtain corresponding second page identity identifier information according to the middleware authentication information;
and the ERP service address acquisition unit is used for matching the first page identification information with the second page identification information, and acquiring the ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
A computer device comprising a memory and a processor, the memory storing a computer program, the processor implementing the following steps when executing the computer program:
when receiving an operation of opening an application page corresponding to a target application, acquiring application authentication information corresponding to the target application and page authentication information of the application page;
acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information;
determining an ERP service address corresponding to the application page according to the first page identity identification information;
and performing page access according to the ERP service address to obtain and display the application page.
A computer-readable storage medium, on which a computer program is stored which, when executed by a processor, carries out the steps of:
when receiving an operation of opening an application page corresponding to a target application, acquiring application authentication information corresponding to the target application and page authentication information of the application page;
acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information;
determining an ERP service address corresponding to the application page according to the first page identity identification information;
and performing page access according to the ERP service address to obtain and display the application page.
According to the method, the device, the computer equipment and the storage medium for acquiring the ERP page, the application authentication information corresponding to the target application and the page authentication information of the application page are acquired through the middleware, and the first page identity information corresponding to the application page is acquired through the application authentication information and the page authentication information; the method comprises the steps of determining an ERP service address corresponding to an application page according to first page identity identification information, carrying out page access according to the ERP service address to obtain and display the application page, achieving the purpose of obtaining page authentication information through the application authentication information and the application page, and setting a corresponding relation between the first page identity identification information and the ERP service address on a middleware.
Drawings
FIG. 1 is a diagram of an application environment of an ERP page acquisition method in one embodiment;
FIG. 2 is a flowchart illustrating an ERP page acquisition method in one embodiment;
FIG. 3 is a flowchart illustrating the ERP service address determination step in one embodiment;
FIG. 4 is a flowchart illustrating a method for sending middleware authentication information according to an embodiment;
fig. 5 is a schematic flowchart of an application authentication information obtaining method corresponding to a target application in an embodiment;
FIG. 6 is a flowchart illustrating an ERP page retrieval method in another embodiment;
FIG. 7 is a flowchart illustrating an ERP page retrieval method in another embodiment;
FIG. 8 is a flowchart illustrating an ERP message pushing method in another embodiment;
FIG. 9 is a block diagram illustrating an embodiment of an ERP page retrieving device;
FIG. 10 is a diagram showing an internal structure of a computer device according to an embodiment.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the present application 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 present application and are not intended to limit the present application.
The ERP page obtaining method provided by the application can be applied to the application environment shown in FIG. 1. The application environment comprises a terminal 102 and an ERP server 104, wherein the terminal 102 comprises a target application and middleware, and the ERP server 104 comprises an ERP service address, and communicates with the server 104 through the terminal 102. When the middleware receives an operation of opening an application page corresponding to a target application, application authentication information corresponding to the target application and page authentication information of the application page are obtained, first page identity identification information corresponding to the application page is obtained according to the application authentication information and the page authentication information, an ERP service address corresponding to the application page is determined according to the first page identity identification information, and page access is carried out according to the ERP service address so as to obtain the application page and display the application page. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices, and the server 104 may be implemented by an independent server or a server cluster formed by a plurality of servers.
In an embodiment, as shown in fig. 2, an ERP page obtaining method is provided, which is described by taking the example that the method is applied to the terminal in fig. 1, and includes the following steps:
step 202, when receiving an operation of opening an application page corresponding to a target application, acquiring application authentication information corresponding to the target application and page authentication information of the application page.
The target application refers to an application that a user needs to access, a computer program which can complete one or more specific tasks, and a visual user interface. E.g., WeChat, OA System or cloud home, etc.; the application page refers to an application page in the target application, and for example, may be a calendar page accessed in the ERP application; the application authentication information corresponding to the target application is unique authentication information capable of opening the target application; the page authentication information of the application page is unique authentication information that enables opening of a certain application page under the target application.
Specifically, when the middleware is installed on the target application, and an operation of opening an application page corresponding to the target application is received, the middleware initiates to acquire the authentication information of the target application and the authentication information of a specific application page in the target application. For example, a middleware is installed on OA (office automation), and when a certain application page on OA, for example, business approval, is opened, the middleware acquires authentication information of the OA and the business approval, and the authentication information may be regarded as a certificate for entering the OA and the business approval of the application page under OA. The middleware is an intermediate component capable of establishing a connection relationship between the target application and the ERP page, and the intermediate component may be software or a hardware module capable of providing an application interface.
In an embodiment, the application authentication information corresponding to the target application may be an acesttoken, the authentication information of the application page may be represented by a socket, and after the middleware is installed on the target application, when an application page under the target application is opened, the middleware may initiate an action of acquiring the aceston and the socket. The AcessToken is a unique certificate for accessing the target application, the AcessToken can be used as authentication information for inquiring the relevant information of the target application, the relevant information of the target application is stored in a database of the server, and the relevant information of the target application can be inquired from the database of the server through the AcessToken. The related information of the target application includes access user information or user access time of the target application. The Ticket is a unique credential for accessing the application page in the target application, the Ticket is a temporary credential capable of accessing the application page in the target application, and when the Ticket is obtained again, the previous Ticket fails.
In one embodiment, a function entry of an application page may be exposed on a target application, and when a trigger operation on the function entry is received, an operation of opening the application page corresponding to the target application is received.
In one embodiment, the function entry may correspond to a preset access address, the access address is fixed, the preset access address may be preferentially used for access, and when it is determined that the application page cannot be accessed according to the access address, the access address is ignored, and step S202 is performed.
And 204, acquiring first page identity information corresponding to the application page according to the application authentication information and the page authentication information.
The first page identification information is unique user identification information capable of opening a page. The application page can store the identity identification information, so that the identity of the user can be conveniently identified when the user logs in next time.
Specifically, the application authentication information and the page authentication information correspond to unique first page identification information, and after the application authentication information and the page authentication information are acquired by the middleware, the corresponding first page identification information is acquired through the application authentication information and the page authentication information. For example, OpenId is used to represent the first page identification information, and after acquiring the application authentication information, accesstken, and the authentication information of the page can use Ticket, the middleware can acquire the corresponding OpenId through the accesstken and Ticket. OpenId is identification information generated when different users use different target applications, and the identification information is stored in the target application used by the user, so that the user can be identified when the user uses the application again.
In one embodiment, OpenId may be bound to an original account used by a user in a target application, so that the user may open an application page in the target application through OpenId; and meanwhile, an application page in the target application can be opened through the original account.
And step 206, determining an ERP service address corresponding to the application page according to the first page identity information.
The ERP service address refers to a network address of an application page, for example, an IP (internet protocol) address corresponding to the application page, and the target application can normally access the corresponding ERP page through the IP address.
Specifically, after the middleware acquires the first page identification information, the ERP service address bound with the first page identification information can be acquired through the identification information.
In one embodiment, the ERP service address corresponding to the application page may be determined by configuring the ERP service address corresponding to the first page identification information on the middleware. However, when the ERP service address changes, the corresponding ERP page cannot be opened through OpenId. For example, after the first page identity information OpenId is acquired by the middleware, there is no binding relationship between the OpenId and the ERP service address, and a connection relationship cannot be established between the application page and the changed IP address of the ERP service, and at this time, the configuration of the IP address of the ERP service needs to be performed on the middleware, so as to establish a binding relationship with the OpenId corresponding to the application page acquired by the middleware, and determine the ERP service address corresponding to the application page through the OpenId.
In one embodiment, the middleware may be a SaaS (Software-as-a-Service) Service, the Software connected with the middleware may be provided with a Service through a network, the target application and the unified domain name used by the ERP as the middleware may be used by the ERP, and the connection between the target application and the ERP may be established through the middleware. The domain names of different target applications can be different, and the domain names of a plurality of corresponding ERPs can also be different, but the domain names of the target applications and the ERPs correspond to the uniform domain name of the middleware, so that the target applications and the ERPs can access the middleware in real time.
And step 208, performing page access according to the ERP service address to obtain and display an application page.
Specifically, after the middleware obtains the ERP service address, the middleware may access the corresponding ERP service address through the determined binding relationship between the ERP service address and the obtained first page identification information, and obtain the ERP page, where the access address of the application page is the ERP service address.
In the ERP page acquisition method, application authentication information corresponding to a target application and page authentication information of an application page are acquired through a middleware, and first page identity information corresponding to the application page is acquired through the application authentication information and the page authentication information; the method comprises the steps of determining an ERP service address corresponding to an application page according to first page identity identification information, carrying out page access according to the ERP service address to obtain and display the application page, achieving the purpose of obtaining page authentication information through the application authentication information and the application page, and setting a corresponding relation between the first page identity identification information and the ERP service address on a middleware.
In one embodiment, as shown in fig. 3, determining the ERP service address corresponding to the application page according to the first page identification information includes:
step 302, acquiring a first network electronic identifier of the application page on the middleware according to the first page identity identification information.
The first network electronic identification refers to identification of first page identity identification information of an application page in the target application on the middleware.
Specifically, after the middleware acquires the first page identification information, an identifier which is obtained by mapping the first page identification information to the middleware can be acquired, and the identifier can be called as a first network electronic identifier which is the only identifier which can represent the first page identification information on the middleware. For example, if the first page id information OpenId1 is "xiaoming 123", and the first network electronic identifier EID (electronic id) on the middleware is "zhangsan 456", the middleware may obtain that the corresponding EID is "zhangsan 456" for "xiaoming 123" according to OpenId 1.
And step 304, determining middleware authentication information of the middleware according to the first network electronic identifier and the first ERP platform identifier corresponding to the application page.
The ERP platform identification is an identification which can uniquely identify the ERP platform on the middleware and is an identification which has a mapping relation with the ERP on the middleware; the middleware authentication information is unique authentication information that enables opening of the middleware.
Specifically, after the middleware acquires the first network electronic identifier of the application page on the middleware through the first page identity identification information, the middleware authentication information of the middleware is determined through the first network electronic identifier and the first ERP platform identifier. For example, the middleware may determine the middleware authentication information accesstken through the received first network electronic identifier EID and the first ERP platform identifier EntryRole.
In one embodiment, the first ERP platform identifier is an identifier on the middleware that has a mapping relationship with the ERP. For example, in order to distinguish different ERP service addresses, the middleware distinguishes the ERP service addresses by the specific content of EntryRole. For example, in the OA application, the EntryRole of the service approval application page in the middleware is 0100, the EntryRole of the palm reimbursement application page in the middleware is 0101, and the like.
And step 306, sending the middleware authentication information to the ERP server corresponding to the first ERP platform identifier, so that the ERP server obtains corresponding second page identity identification information according to the middleware authentication information.
The ERP server is a server containing at least one ERP address; the second page identity information refers to page identity information corresponding to the middleware authentication information acquired by the ERP server according to the middleware authentication information.
Specifically, after the middleware acquires the middleware authentication information, the middleware authentication information is sent to the ERP server corresponding to the first ERP platform identifier, and after the ERP server receives the middleware authentication information, the second page identity identifier information is analyzed according to the middleware authentication information. For example, after the middleware receives the middleware authentication information AccessToken, the middleware authentication information accesstken is sent to the corresponding ERP server through the EntryRole on the middleware, and after the ERP server receives the middleware authentication information accesstken, the second page identity information OpenId2 is analyzed according to the middleware authentication information accesstken.
And 308, matching the first page identification information with the second page identification information, and acquiring an ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
Specifically, the middleware compares the received first page identification information with second page identification information analyzed by the ERP server, and when the two page identification information are matched, a binding relationship exists between the first page identification information and the ERP service address, so that the terminal can acquire a corresponding ERP page through an application page in a target application.
In an embodiment, after the middleware sends the middleware authentication information to the ERP server, the ERP server parses the middleware authentication information to obtain the second page identification information, where the middleware authentication information corresponds to the first network electronic identifier EID, and the first network electronic identifier EID corresponds to the first page identification information OpenId1, and at this time, the second page identification information OpenId2 obtained by the ERP server is the same as the first page identification information OpenId 1. When the second page identity information OpenId2 has a binding relationship with an ERP service address on the ERP server, directly jumping to the corresponding ERP service address through the second page identity information OpenId 2.
In this embodiment, a first network electronic identifier of the middleware is obtained through the first page identity identifier information, the middleware authentication information is determined through the first ERP platform identifier through the first network electronic identifier and the first ERP platform identifier, and the middleware authentication information is sent to the ERP server, so that the ERP server obtains second page identity identifier information through the middleware authentication information, the middleware matches the obtained first page identity identifier information and the obtained second page identity identifier information, and the purpose of determining an ERP service address corresponding to an application page by the first page identity identifier information can be achieved.
In one embodiment, the ERP page obtaining method further includes:
and when the first page identification information is not matched with the second page identification information, displaying an ERP service address setting page corresponding to the application page, and acquiring the binding relationship between the first page identification information and the ERP service address through the service address setting page.
Specifically, when the first page identification information acquired in the middle is not matched with the second page identification information, an ERP service address setting page corresponding to the application page is displayed on the middleware, and a corresponding ERP service address can be bound. For example, a new ERP service address bound with the first page identification information is set on the middleware, so that when an application page in the target application is opened, the ERP service address corresponding to the application page can be successfully acquired.
In an embodiment, when an analysis error occurs in the process of analyzing the middleware authentication information by the ERP service, a situation that the first page identification information is not matched with the second page identification information also occurs, and the binding of the ERP service address and the first page identification information can also be realized by resetting the ERP service address on the middleware.
In this embodiment, by matching the first page identification information with the second page identification information, the purpose of configuring a new ERP service address on the middleware can be achieved, and the stability of the ERP page can be achieved under the condition that the ERP service address changes or the page identification information is analyzed incorrectly.
In one embodiment, as shown in fig. 4, sending the middleware authentication information to the ERP server corresponding to the first ERP platform identifier includes:
and 402, receiving an encrypted public key corresponding to the ERP server.
The public key is a key for encrypting or decrypting encrypted content, which is disclosed to the outside.
Specifically, before sending the middleware authentication information of the local end to the ERP server, the middleware first receives a public key sent by the ERP server for encryption protection, so that the middleware encrypts the middleware authentication information according to the public key.
At step 404, the middleware authentication information is encrypted by using the encrypted public key to form encrypted middleware authentication information.
Specifically, after receiving the public key sent by the ERP server, the middleware encrypts the middleware authentication information by using the public key, thereby forming encrypted middleware authentication information.
Step 406, adding a signature to the encrypted middleware authentication information by using a local private key to obtain signed middleware authentication information;
the private key is a key which is reserved at the local end and can only decrypt or encrypt the encrypted content at the local end.
Specifically, after receiving the encrypted middleware authentication information, the middleware signs the encrypted middleware authentication information by using the private key of the middleware, and acquires the signed middleware authentication information.
And step 408, sending the signed middleware authentication information to the ERP server.
Specifically, after signing the encrypted middleware authentication information, the middleware sends the signed middleware authentication information to the ERP server, so that the ERP server can verify the signature by using the public key of the middleware, ensure that the information is sent by the middleware, decrypt the information by using the private key of the server, and ensure the accuracy of transmission of the middleware authentication information. In the embodiment, the middleware authentication information is transmitted in an encryption and signature mode, so that the accuracy and the safety of message transmission between the middleware and the ERP server can be achieved.
In one embodiment, as shown in fig. 5, acquiring the application authentication information corresponding to the target application includes:
The application identifier of the application page is a unique identifier capable of being applied to the application page at random; the page key of the application page refers to a password that can open the application page.
Specifically, the target application stores an application identifier of an application page in the target application and a page key of the application page; in the process of installing the middleware in the target application, the middleware acquires the application identifier of the application page and the page key of the application page in the target application. For example, when a user installs middleware in the OA, the middleware obtains the application identification AppId1 for mobile sale of one of the application pages in the OA and the application key.
And step 504, acquiring application authentication information corresponding to the target application according to the page identifier and the page key.
Specifically, after the application identifier of the application page and the page key of the application page are obtained, the middleware may obtain the application authentication information corresponding to the target application according to the application identifier of the application page and the page key of the application page. For example, after the middleware acquires the application identifier AppId1 of the application page and the page key of the application page, the middleware acquires the application authentication information accesstken corresponding to the target application through the AppId1 and AppId1 keys.
In this embodiment, the application authentication information corresponding to the target application is obtained through the application identifier of the application page and the page key of the application page, so that the purpose of obtaining the application authentication information corresponding to the target application when the middleware is installed can be achieved.
In one embodiment, as shown in fig. 6, the ERP page obtaining method further includes:
step 602, when receiving a push message from the ERP push server, obtaining a second ERP platform identifier corresponding to the ERP push server, a push page identifier corresponding to a push message display page, and a second network electronic identifier corresponding to the push message display page.
Specifically, when the middleware receives a push message of the ERP push server, first, the second ERP platform identifier EntryRole2 of the middleware home end corresponding to the ERP push server, the page identifier AppId2 corresponding to a page that needs to display the push message, and the second network electronic identifier EID2 on the middleware corresponding to a corresponding application page that the middleware home end needs to push the message are obtained, and the AppId2 corresponding to the second network electronic identifier EID2 is obtained.
And step 604, determining a message pushing interface according to the second ERP platform identifier, the pushing page identifier and the second network electronic identifier.
The message pushing interface refers to a unique interface capable of pushing messages on the middleware.
Specifically, a one-to-one correspondence relationship exists between the second ERP platform identifier, the push page identifier, the second network electronic identifier, and the message push interface can be determined according to the second ERP platform identifier, the push page identifier, and the second network electronic identifier. For example, the second ERP platform identity EntryRole2 may determine the interface of the ERP push message to the middleware, the second network electronic identity EID2 may determine which target application to send to, the push page identity AppId2 may determine which application page to send to,
step 606, push the push message to the push message display page through the message push interface.
Specifically, after determining the message push interface on the middleware, the ERP may send the message to the corresponding application page with the push page identifier AppId2 through the push interface by using the second ERP platform identifier EntryRole2 on the middleware.
In this embodiment, by setting the corresponding interface, the push page identifier, and the push message interface of the ERP push server on the middleware, the message pushed by the ERP push server can be pushed to the corresponding push page.
In an embodiment, as shown in fig. 7, when a user opens a target application, a middleware installed in the target application may obtain authentication information AccessToken of the target application and authentication information Ticket of an application page of the target application, and may obtain a unique user identifier OpenId for opening the application page through the AccessToken and Ticket. The middleware is provided with an identifier EID corresponding to the only user identifier OpenId of the application page and an identifier EntryRole corresponding to the ERP, the middleware can package information such as OpenId and the like to form a data packet, and the data packet is sent to an ERP address server corresponding to a corresponding ERP service address through the configuration rule according to the one-to-one configuration rule; the ERP address server decrypts the data packet sent by the middleware to obtain the Access token of the middleware and the unique user identifier OpenId of the application page after decryption; if the OpenId and the ERP service address have a binding relation, jumping to the corresponding ERP service address through the middleware; and if the OpenId and the ERP service address are not in a binding relationship, jumping to a corresponding ERP service address setting page on the middleware, and setting the ERP service address, so that when the ERP service address changes, a user can also accurately acquire the ERP page. The access token of the middleware is sent to the middleware through the AppId and the APP key generated by the target application when the middleware is installed in the target application, and the middleware can acquire the access token of the target application through the AppId and the APP key, and the access token and the authentication information access token of the target application are the same access token.
In an embodiment, as shown in fig. 8, when the ERP server needs to push a message to a corresponding target application, the pushed message includes an EntryRole, an AppId, an EID, and a message body, and after receiving the EntryRole, the AppId, the EID, and the message body, the middleware acquires a corresponding sutetetoken through the EntryRole and the EID; the SuiteToken is sent to the middleware after the target should be acquired through the EID and the AppId. The message body comprises a message type and a message content, and can be considered as an interface parameter between the ERP server and the middleware, and different message bodies correspond to interfaces of different middleware. For example, a message sent to the nailing platform is converted according to the message format of the nail, a message sent to the enterprise wechat platform is converted according to the message format of the enterprise wechat, and the like. The middleware converts the message body into a parameter format corresponding to the target application after receiving the message body, wherein the parameter format is in a text card format and comprises at least one of a title, content and a link address. And requesting a corresponding pushing interface from the target application, and pushing the pushing message to the target application through the pushing interface. The target application returns a corresponding message identifier MsgId, the middleware records a corresponding message pushing result, if the message identifier of the pushing result contains BizId which represents a message to be handled, the ERP server pushes the corresponding BizId, the message pushing record is recorded through the BizId, the target application updates a port to be handled, the conversion from the handling to the handling is realized, and the domain name in the message link uses the uniform domain name of the middleware. When the user clicks the message, the user enters a transit link address of a transit server of the ERP and enters an ERP service address through the transit link address.
In one embodiment, the target application may be an office suite, such as an OA system or enterprise WeChat, etc.; and the office suite is provided with a middleware. Related configuration of ERP is carried out in the middleware. For example, an ERP service address is configured on the middleware, and the service address may be an IP address through which a corresponding ERP page can be accessed. The multiple ERP service addresses can be configured on the middleware, and the user can open corresponding different office suites or different applications under the office suites through the configured multiple ERP service addresses.
In one embodiment, when the ERP service address corresponding to different applications in the office suite or the office suite changes, a new ERP service address may be newly configured on the middleware, and secondary development of the office suite or the ERP is not required, for example, the ERP is upgraded or a patch version of the ERP corresponding to the new office suite is searched. Meanwhile, after the ERP pushes the message to the office suite, when the user opens the message link by using the office suite, the middleware skips through the configured new ERP address, and the history message viewing is not influenced.
In one embodiment, the communication between the ERP and the middleware adopts RSA public key verification signature, key decryption, and RSA encryption is an asymmetric encryption. Decryption can be done without directly passing the key. The method can ensure the safety of information, avoid the risk of being cracked caused by directly transmitting the secret key, and ensure the safety of the interface.
It should be understood that although the various steps in the flow charts of fig. 1-6 are shown in order as indicated by the arrows, the steps are not necessarily performed in order as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least some of the steps in fig. 1-6 may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, which are not necessarily performed in sequence, but may be performed in turn or alternately with other steps or at least some of the other steps.
In one embodiment, as shown in fig. 9, an ERP page obtaining apparatus 900 is provided, which includes: an application authentication information and page authentication information obtaining module 902, a first page identity information obtaining module 904, an ERP service address obtaining module 906, and an application page obtaining and displaying module 908, wherein:
an application authentication information and page authentication information obtaining module 902, configured to, when receiving an operation of opening an application page corresponding to a target application, obtain application authentication information corresponding to the target application and page authentication information of the application page;
a first page identity information obtaining module 904, configured to obtain, according to the application authentication information and the page authentication information, first page identity information corresponding to the application page;
an ERP service address obtaining module 906, configured to determine, according to the first page identity information, an ERP service address corresponding to the application page;
and the application page obtaining and displaying module 908 is used for performing page access according to the ERP service address to obtain and display an application page.
In one embodiment, the ERP service address acquisition module 906 comprises: the system comprises a first network electronic identification obtaining unit, a middleware authentication information determining unit, a middleware authentication information sending unit and an ERP service address obtaining unit.
The first network electronic identification acquisition unit is used for acquiring a first network electronic identification of the application page on the middleware according to the first page identity identification information;
the middleware authentication information determining unit is used for determining the middleware authentication information of the middleware according to the first network electronic identifier and the first ERP platform identifier corresponding to the application page;
the middleware authentication information sending unit is used for sending the middleware authentication information to the ERP server corresponding to the first ERP platform identifier so that the ERP server can obtain corresponding second page identity identifier information according to the middleware authentication information;
and the ERP service address acquisition unit is used for matching the first page identification information with the second page identification information, and acquiring an ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
In one embodiment, the ERP service address obtaining unit is further configured to, when the ERP service address obtaining unit does not match the ERP service address obtaining unit, display an ERP service address setting page corresponding to the application page;
and acquiring the binding relationship between the first page identity identification information and the ERP service address through the service address setting page.
In one embodiment, the middleware authentication information sending unit is further configured to: receiving an encrypted public key corresponding to the ERP server;
encrypting the middleware authentication information by using the encryption public key to form encrypted middleware authentication information;
adding a signature to the encrypted middleware authentication information by using a local private key to obtain signed middleware authentication information;
and sending the signed middleware authentication information to the ERP server.
In one embodiment, the application authentication information and page authentication information acquisition module includes: an application identifier and page key acquisition unit and an application authentication information acquisition unit, wherein:
the application identification and page key acquisition unit is used for acquiring the application identification of the application page and the page key of the application page;
and the application authentication information acquisition unit is used for acquiring the application authentication information corresponding to the target application according to the page identifier and the page key.
In one embodiment, the ERP page obtaining device further includes: a second ERP platform identifier, a pushed page identifier, a second network electronic identifier obtaining module, a message pushing interface determining module and a message pushing module, wherein:
and the second ERP platform identifier, the push page identifier and the second network electronic identifier acquisition module are used for acquiring a second ERP platform identifier corresponding to the ERP push server, a push page identifier corresponding to the push message display page and a second network electronic identifier corresponding to the push message display page when receiving a push message of the ERP push server.
And the message pushing interface determining module is used for determining a message pushing interface according to the second ERP platform identifier, the pushing page identifier and the second network electronic identifier.
And the message pushing module is used for pushing the pushing message to a pushing message display page through a message pushing interface.
For specific limitations of the ERP page obtaining device, refer to the above limitations on the ERP page obtaining method, which are not described herein again. All or part of each module in the ERP page acquisition device can be realized by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 10. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile 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 an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, an operator network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement an ERP page retrieval method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.
Those skilled in the art will appreciate that the architecture shown in fig. 10 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.
In one embodiment, a computer device is provided, comprising a memory and a processor, the memory having a computer program stored therein, the processor implementing the following steps when executing the computer program:
when receiving an operation of opening an application page corresponding to a target application, acquiring an application corresponding to the target application
Using the authentication information and the page authentication information of the application page;
acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information;
determining an ERP service address corresponding to the application page according to the first page identity identification information;
and performing page access according to the ERP service address to obtain and display an application page.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring a first network electronic identifier of the application page on the middleware according to the first page identity identification information;
determining middleware authentication information of the middleware according to the first network electronic identifier and a first ERP platform identifier corresponding to the application page;
sending the middleware authentication information to an ERP server corresponding to the first ERP platform identifier, so that the ERP server obtains corresponding second page identity identifier information according to the middleware authentication information;
and matching the first page identification information with the second page identification information, and acquiring an ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
when the ERP service addresses are not matched, displaying an ERP service address setting page corresponding to the application page;
and acquiring the binding relationship between the first page identity identification information and the ERP service address through the service address setting page.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
receiving an encrypted public key corresponding to the ERP server;
encrypting the middleware authentication information by using the encryption public key to form encrypted middleware authentication information;
adding a signature to the encrypted middleware authentication information by using a local private key to obtain signed middleware authentication information;
and sending the signed middleware authentication information to the ERP server.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
acquiring an application identifier of an application page and a page key of the application page;
and acquiring application authentication information corresponding to the target application according to the page identifier and the page key.
In one embodiment, the processor, when executing the computer program, further performs the steps of:
when a push message of an ERP push server is received, acquiring a second ERP platform identifier corresponding to the ERP push server, a push page identifier corresponding to a push message display page and a second network electronic identifier corresponding to the push message display page;
determining a message pushing interface according to the second ERP platform identifier, the pushing page identifier and the second network electronic identifier;
and pushing the push message to a push message display page through a message pushing interface.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
when receiving an operation of opening an application page corresponding to a target application, acquiring an application corresponding to the target application
Using the authentication information and the page authentication information of the application page;
acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information;
determining an ERP service address corresponding to the application page according to the first page identity identification information;
and performing page access according to the ERP service address to obtain and display an application page.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring a first network electronic identifier of the application page on the middleware according to the first page identity identification information;
determining middleware authentication information of the middleware according to the first network electronic identifier and a first ERP platform identifier corresponding to the application page;
sending the middleware authentication information to an ERP server corresponding to the first ERP platform identifier, so that the ERP server obtains corresponding second page identity identifier information according to the middleware authentication information;
and matching the first page identification information with the second page identification information, and acquiring an ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
In one embodiment, the computer program when executed by the processor further performs the steps of:
when the ERP service addresses are not matched, displaying an ERP service address setting page corresponding to the application page;
and acquiring the binding relationship between the first page identity identification information and the ERP service address through the service address setting page.
In one embodiment, the computer program when executed by the processor further performs the steps of:
receiving an encrypted public key corresponding to the ERP server;
encrypting the middleware authentication information by using the encryption public key to form encrypted middleware authentication information;
adding a signature to the encrypted middleware authentication information by using a local private key to obtain signed middleware authentication information;
and sending the signed middleware authentication information to the ERP server.
In one embodiment, the computer program when executed by the processor further performs the steps of:
acquiring an application identifier of an application page and a page key of the application page;
and acquiring application authentication information corresponding to the target application according to the page identifier and the page key.
In one embodiment, the computer program when executed by the processor further performs the steps of:
when a push message of an ERP push server is received, acquiring a second ERP platform identifier corresponding to the ERP push server, a push page identifier corresponding to a push message display page and a second network electronic identifier corresponding to the push message display page;
determining a message pushing interface according to the second ERP platform identifier, the pushing page identifier and the second network electronic identifier;
and pushing the push message to a push message display page through a message pushing interface.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware related to instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database or other medium used in the embodiments provided herein can 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, optical storage, or the like. Volatile Memory can include Random Access Memory (RAM) or external cache Memory. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others.
The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.
The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present patent shall be subject to the appended claims.
Claims (10)
1. An ERP page acquisition method is applied to middleware and is characterized by comprising the following steps:
when receiving an operation of opening an application page corresponding to a target application, acquiring application authentication information corresponding to the target application and page authentication information of the application page;
acquiring first page identity identification information corresponding to the application page according to the application authentication information and the page authentication information;
determining an ERP service address corresponding to the application page according to the first page identity identification information;
and performing page access according to the ERP service address to obtain and display the application page.
2. The method according to claim 1, wherein the determining the ERP service address corresponding to the application page according to the first page identification information includes:
acquiring a first network electronic identifier of the application page on the middleware according to the first page identity identification information;
determining middleware authentication information of the middleware according to the first network electronic identifier and a first ERP platform identifier corresponding to the application page;
sending the middleware authentication information to an ERP server corresponding to the first ERP platform identification, so that the ERP server obtains corresponding second page identity identification information according to the middleware authentication information;
and matching the first page identification information with the second page identification information, and acquiring the ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
3. The method of claim 2, further comprising:
when the ERP service addresses are not matched, displaying an ERP service address setting page corresponding to the application page;
and acquiring the binding relationship between the first page identity identification information and the ERP service address through the service address setting page.
4. The method of claim 2, wherein sending the middleware authentication information to the ERP server corresponding to the first ERP platform identification comprises:
receiving an encrypted public key corresponding to the ERP server;
encrypting the middleware authentication information by using the encryption public key to form encrypted middleware authentication information;
adding a signature to the encrypted middleware authentication information by using a local private key to obtain signed middleware authentication information;
and sending the signed middleware authentication information to the ERP server.
5. The method according to claim 1, wherein the obtaining application authentication information corresponding to the target application comprises:
acquiring an application identifier of the application page and a page key of the application page;
and acquiring application authentication information corresponding to the target application according to the page identifier and the page key.
6. The method of claim 1, further comprising:
when a push message of an ERP push server is received, acquiring a second ERP platform identifier corresponding to the ERP push server, a push page identifier corresponding to a push message display page and a second network electronic identifier corresponding to the push message display page;
determining a message pushing interface according to the second ERP platform identification, the pushing page identification and the second network electronic identification;
and pushing the push message to the push message display page through the message pushing interface.
7. An ERP page obtaining apparatus, characterized in that the apparatus comprises:
the application authentication information and page authentication information acquisition module is used for acquiring application authentication information corresponding to a target application and page authentication information of the application page when receiving an operation of opening the application page corresponding to the target application;
the first page identity information acquisition module is used for acquiring first page identity information corresponding to the application page according to the application authentication information and the page authentication information;
the ERP service address acquisition module is used for determining an ERP service address corresponding to the application page according to the first page identity identification information;
and the application page acquisition and display module is used for carrying out page access according to the ERP service address so as to acquire and display the application page.
8. The apparatus of claim 7, wherein the ERP service address obtaining module comprises:
the first network electronic identification acquisition unit is used for acquiring a first network electronic identification of the application page on the middleware according to the first page identity identification information;
the middleware authentication information determining unit is used for determining the middleware authentication information of the middleware according to the first network electronic identifier and the first ERP platform identifier corresponding to the application page;
the middleware authentication information sending unit is used for sending the middleware authentication information to an ERP server corresponding to the first ERP platform identifier so that the ERP server can obtain corresponding second page identity identifier information according to the middleware authentication information;
and the ERP service address acquisition unit is used for matching the first page identification information with the second page identification information, and acquiring the ERP service address according to the first page identification information when the first page identification information is matched with the second page identification information.
9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 6.
10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011293221.4A CN112464259B (en) | 2020-11-18 | 2020-11-18 | ERP page acquisition method, ERP page acquisition device, computer equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011293221.4A CN112464259B (en) | 2020-11-18 | 2020-11-18 | ERP page acquisition method, ERP page acquisition device, computer equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112464259A true CN112464259A (en) | 2021-03-09 |
| CN112464259B CN112464259B (en) | 2024-04-30 |
Family
ID=74836091
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011293221.4A Active CN112464259B (en) | 2020-11-18 | 2020-11-18 | ERP page acquisition method, ERP page acquisition device, computer equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112464259B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113556391A (en) * | 2021-07-16 | 2021-10-26 | 北京达佳互联信息技术有限公司 | Page communication method and device, electronic equipment and readable storage medium |
Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050040675A (en) * | 2003-10-28 | 2005-05-03 | 주식회사 매티코리아 | Erp system for supporting guidance with realtime and thereof method |
| CN101287018A (en) * | 2008-05-09 | 2008-10-15 | 金蝶软件（中国）有限公司 | Integrated data-handling method and device based on multi-system user |
| US20120192261A1 (en) * | 2009-09-30 | 2012-07-26 | Trustseed Sas | System and method for the management of secure electronic correspondence sessions |
| US20120278854A1 (en) * | 2011-04-27 | 2012-11-01 | Andrew Ton | System and method for device addressing |
| CN102930401A (en) * | 2011-11-09 | 2013-02-13 | 微软公司 | Technology providing enterprise resource planning (ERP) function from customer relation management (CRM) client side application |
| US20130103584A1 (en) * | 2011-10-25 | 2013-04-25 | Paymintz, Inc. | Payment service that provides option to authenticate with external authentication service |
| US20130117055A1 (en) * | 2011-11-09 | 2013-05-09 | Microsoft Corporation | Techniques to provide enterprise resource planning functions from an e-mail client application |
| US20130212170A1 (en) * | 2012-02-09 | 2013-08-15 | Oracle International Corporation | Quantify and measure micro-blogging for enterprise resources planning (erp) |
| CN103729902A (en) * | 2012-10-15 | 2014-04-16 | 金蝶软件（中国）有限公司 | Attendance checking sign-in method, attendance checking register method, attendance checking terminal and attendance checking server |
| US20160098779A1 (en) * | 2014-10-02 | 2016-04-07 | Coupa Software Incorporated | Providing access to a networked application without authentication |
| CN105718466A (en) * | 2014-12-02 | 2016-06-29 | 金蝶软件（中国）有限公司 | Method and system for transferring data between platforms |
| US20180075231A1 (en) * | 2016-09-14 | 2018-03-15 | Oracle International Corporation | Single sign-on functionality for a multi-tenant identity and data security management cloud service |
| CN108418797A (en) * | 2018-01-31 | 2018-08-17 | 金蝶蝶金云计算有限公司 | Web access method, device, computer equipment and storage medium |
| CN109246146A (en) * | 2018-11-01 | 2019-01-18 | 北京京航计算通讯研究所 | SAP ERP single-point logging method based on JAVA middleware intergration model |
| CN110910186A (en) * | 2018-09-14 | 2020-03-24 | 北京京东尚科信息技术有限公司 | Method and device for transmitting user information |
| CN111404921A (en) * | 2020-03-12 | 2020-07-10 | 广州市百果园信息技术有限公司 | Webpage application access method, device, equipment, system and storage medium |
| CN111917711A (en) * | 2020-06-15 | 2020-11-10 | 广州市设计院 | Data access method and device, computer equipment and storage medium |
-
2020
- 2020-11-18 CN CN202011293221.4A patent/CN112464259B/en active Active
Patent Citations (17)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| KR20050040675A (en) * | 2003-10-28 | 2005-05-03 | 주식회사 매티코리아 | Erp system for supporting guidance with realtime and thereof method |
| CN101287018A (en) * | 2008-05-09 | 2008-10-15 | 金蝶软件（中国）有限公司 | Integrated data-handling method and device based on multi-system user |
| US20120192261A1 (en) * | 2009-09-30 | 2012-07-26 | Trustseed Sas | System and method for the management of secure electronic correspondence sessions |
| US20120278854A1 (en) * | 2011-04-27 | 2012-11-01 | Andrew Ton | System and method for device addressing |
| US20130103584A1 (en) * | 2011-10-25 | 2013-04-25 | Paymintz, Inc. | Payment service that provides option to authenticate with external authentication service |
| CN102930401A (en) * | 2011-11-09 | 2013-02-13 | 微软公司 | Technology providing enterprise resource planning (ERP) function from customer relation management (CRM) client side application |
| US20130117055A1 (en) * | 2011-11-09 | 2013-05-09 | Microsoft Corporation | Techniques to provide enterprise resource planning functions from an e-mail client application |
| US20130212170A1 (en) * | 2012-02-09 | 2013-08-15 | Oracle International Corporation | Quantify and measure micro-blogging for enterprise resources planning (erp) |
| CN103729902A (en) * | 2012-10-15 | 2014-04-16 | 金蝶软件（中国）有限公司 | Attendance checking sign-in method, attendance checking register method, attendance checking terminal and attendance checking server |
| US20160098779A1 (en) * | 2014-10-02 | 2016-04-07 | Coupa Software Incorporated | Providing access to a networked application without authentication |
| CN105718466A (en) * | 2014-12-02 | 2016-06-29 | 金蝶软件（中国）有限公司 | Method and system for transferring data between platforms |
| US20180075231A1 (en) * | 2016-09-14 | 2018-03-15 | Oracle International Corporation | Single sign-on functionality for a multi-tenant identity and data security management cloud service |
| CN108418797A (en) * | 2018-01-31 | 2018-08-17 | 金蝶蝶金云计算有限公司 | Web access method, device, computer equipment and storage medium |
| CN110910186A (en) * | 2018-09-14 | 2020-03-24 | 北京京东尚科信息技术有限公司 | Method and device for transmitting user information |
| CN109246146A (en) * | 2018-11-01 | 2019-01-18 | 北京京航计算通讯研究所 | SAP ERP single-point logging method based on JAVA middleware intergration model |
| CN111404921A (en) * | 2020-03-12 | 2020-07-10 | 广州市百果园信息技术有限公司 | Webpage application access method, device, equipment, system and storage medium |
| CN111917711A (en) * | 2020-06-15 | 2020-11-10 | 广州市设计院 | Data access method and device, computer equipment and storage medium |
Non-Patent Citations (3)
| Title |
|---|
| 刘素芳;: "面向ERP协同办公的移动中间件技术应用研究", 淮阴师范学院学报(自然科学版), no. 04, pages 313 - 317 * |
| 熊丽婷;: ""互联网+"模式下的票务开发平台API设计", 信息系统工程, no. 11, pages 114 - 115 * |
| 翟欣;李敏波;李华;: "RFID应用系统与ERP系统间的业务集成", 计算机应用与软件, no. 08, pages 94 - 96 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113556391A (en) * | 2021-07-16 | 2021-10-26 | 北京达佳互联信息技术有限公司 | Page communication method and device, electronic equipment and readable storage medium |
| CN113556391B (en) * | 2021-07-16 | 2023-11-21 | 北京达佳互联信息技术有限公司 | Page communication method, device, electronic equipment and readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112464259B (en) | 2024-04-30 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110365670B (en) | Blacklist sharing method and device, computer equipment and storage medium | |
| US20210157938A1 (en) | Methods, media, apparatuses and computing devices of user data authorization based on blockchain | |
| US9766914B2 (en) | System and methods for remote maintenance in an electronic network with multiple clients | |
| US9294550B2 (en) | Efficient data transfer for cloud storage by centralized management of access tokens | |
| CN110858249B (en) | Database file encryption method, database file decryption method and related devices | |
| CN104144419A (en) | Identity authentication method, device and system | |
| CN104580316A (en) | Software authorization management method and software authorization management system | |
| CN105516059B (en) | A kind of resource access control method and device | |
| CN110889131B (en) | File sharing system | |
| CN110719590B (en) | One-key login method, device, equipment and storage medium based on mobile phone number | |
| CN109039997B (en) | Secret key obtaining method, device and system | |
| CN111259364B (en) | Method, device, equipment and storage medium for using national secret encryption card | |
| CN113297559A (en) | Single sign-on method and device, computer equipment and storage medium | |
| JP5086839B2 (en) | Authentication device, biometric information management apparatus, authentication system, and authentication method | |
| CN112399392A (en) | Communication connection method, device, equipment and storage medium of home care terminal | |
| CN112464259B (en) | ERP page acquisition method, ERP page acquisition device, computer equipment and storage medium | |
| CN114448722B (en) | Cross-browser login method and device, computer equipment and storage medium | |
| CN111259363A (en) | Service access information processing method, system, device, equipment and storage medium | |
| CN112769565A (en) | Method and device for upgrading cryptographic algorithm, computing equipment and medium | |
| TWI441534B (en) | A method of the data transmission of the mobile phone and the system therefore | |
| CN112543194A (en) | Mobile terminal login method and device, computer equipment and storage medium | |
| CN111369307A (en) | Electronic invoice management method and device | |
| CN113961970B (en) | Cross-network-segment network disk login identity authentication method and device, network disk and storage medium | |
| CN113742663B (en) | Watermark file acquisition method and device and electronic equipment | |
| CN113783835B (en) | Password sharing method, device, equipment and 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 | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |