Multiple encryption methods for service providers to transmit business messages

Abstract

The invention discloses a multiple encryption method for a service provider to transmit service messages, including a service provider H5 end, a service provider gateway server end, a service provider authentication end, and a service provider back end, and each end interacts. The present invention solves the problems in the prior art that the service provider service access to the third party will lead to data leakage, uncontrollable data use, increase in the size of the third-party APP, long access cycle and complicated process, and relatively high development cost. The high problem is to provide multiple encryption methods for the service provider to transmit business messages. When it is applied, the entire H5 application is developed by the service provider, and the data will not leak to any third party, and there is no increase in the size of the third-party APP. And the problem that needs to be republished, just need to configure a jump in the third-party background, first have the access key, then the access key, add random number, hash, AES encryption algorithm, public key and private key encryption and decryption Etc. mixing increases the complexity, and the cracking cost of the whole method is very high.

Description

technical field [0001] The invention relates to a computer network security verification access technology, in particular to a multiple encryption method for a service provider to transmit service messages. Background technique [0002] The existing third-party access service provider service methods can be roughly divided into two categories: (1) interface access methods. The service provider provides the interface, and the third party submits the request and obtains the returned data through the background request service provider interface; (2) SDK access method. The third party introduces the service provider's SDK to join its own APP, and requests to call the service provider's interface to submit the request and obtain the returned data through the method provided by the SDK. [0003] Because the interface access method is initiated by a third-party background service, rather than a direct request from the front-end code, the service provider interface is not exposed ...

AI Technical Summary

Problems solved by technology

[0013] The present invention solves the problems in the prior art that the service provider service access to the third party will lead to data leakage, uncontrollable data use, increase in the size of the third-party APP, long access cycle and complicated process, and relatively high development cost. The high problem is to provide multiple encryption methods for the service provider to transmit business messages. When it is applied, the entire H5 application is developed by the service provider, and the data will not leak to any third party, and there is no increase in the size of the third-party APP. For problems that require reissue, only a third-party background configuration is required, and the entire development cost is controllable. Modifications are synchronized with all access parties, no perceptual updates, fast online speed, strong reusability, and To achieve flow control, you can classify the requester according to the key to limit the flow and reject it. First, there is the access key, and then there is the access key, adding random numbers, hashes, AES encryption algorithms, public key private key encryption and decryption, etc. Mixing increases complexity, and the cracking cost of the whole method is very high

Images