gematik1/erp-vau-proxy-client repository overview

⁠VAU-Proxy-Client (VPC)

Technically, the VPC is also a server to its clients. It takes incoming HTTP requests and tries to find a matching route in the application.yaml file. If a matching route is found, the request is either encrypted using VAU encryption and sent to the VPS, or it is redirected without change. If a matching route is not found, an error is returned. If encryption is required, the VPC performs a handshake with the VPS to exchange encryption keys. In this process, the VPC

⁠VPC routes configuration

To register routes, you need to configure the application.yaml file in the VPC. Spring profiles can be used to configure different route profiles. This can also be achieved via Docker environment variables.

vau-proxy-server:
  url: https://my-vau-server:9020
  direct-redirects:
    '[/from]': /to
  cid-redirects:
    - /VAU-Status

To add a non-VAU route, add a new key-value under direct-redirects.

To add a VAU route, add a new key-value under cid-redirects. All VAU routes are automatically redirected to the VPS's /{cid} endpoint, which is assigned to the VPC during the handshake.

Do not remove the /VAU-Status entry, as it is used to check the status of the VAU encryption.

is assigned a unique cid (client ID) that is used for all following VAU requests.

Responses from the VPS are decrypted and returned to the client.