SecureApi DocumentSecureApi Document
Home
Get Start
Version History
  • China Mainland
  • International
  • 简体中文
  • English
Home
Get Start
Version History
  • China Mainland
  • International
  • 简体中文
  • English
  • Start
  • Guide

    • Install
    • Configuration
    • Try It
    • Annotation
    • Url Pattern
    • Exception Handle
    • Encryption Algorithm
    • CipherUtils
    • Two Modes
    • DH Key Agreement
    • Digital Signature Verification
  • Js Demo
  • Best Practice
  • Microservice Invocation
  • Black King Kong

Microservice Invocation

  • Microservices generally use Dubbo or OpenFeign for remote calls, as shown below, right? You can directly call the Interface method to call other microservices modules.
Microservice invocation interface
Microservice invocation interface
  • At present, SecureApi cannot automatically encrypt the parameters on the interface method. The caller needs to manually encrypt the parameters and send a request, that is, @Autowired injects the CipherUtils manually encrypted str provided by SecureApi, and then calls the "feign" method to pass the encrypted "str" in.

  • Then the caller also introduces SecureApi. Each module of microservices sets the same encryption mode and key. There is no need for manual operation on the caller's side. Parameter decipher and return value encryption will be automated.

WARNING

That is to say, the caller currently needs to manually encrypt parameters, and subsequent versions will add support for automatic encryption parameters for microservices calls. Coming soon...

Edit on GitHub
Last Updated:
Contributors: XuYijie
Prev
Best Practice
Next
Black King Kong