Push/Pull Dataflows

The proxy service implements three dataflows:

  • Detokenize outbound pull requests to a Target Web Service

  • Tokenize pull request responses from a Target Web Service.

  • Tokenize inbound push requests from a Target Web Service.

This documentation describes all HTTPS requests in terms of a two-way conversation between Your Server and a Target Web Service. The AuvProxy sits in the middle of this conversation.

Pull Requests

Pull requests originate at Your Server. Your Server starts the transaction by POSTing an HTTPS request to the AuvProxy service.

../_images/pull-overview.svg

The AuvProxy:

  • forwards the unmodified request to the Target Web Service; or

  • detokenizes or tokenizes the request before forwarding it.

The Target Web Service response flows back through the AuvProxy service, which:

  • returns the unmodified response to Your Server; or

  • tokenizes or detokenizes the response before returning it.

Push Requests

Push requests originate from a third-party service POSTing to Your Web Service through the AuvProxy service. In this instance, your web service is considered the Target Web Service.

../_images/push-overview.svg

The AuvProxy:

  • forwards the unmodified push request to the Your Web Service; or

  • detokenizes or tokenizes the request before forwarding it.

Your Web Service response flows through the AuvProxy service, which:

  • returns the unmodified response to the Target Web Service; or

  • tokenizes or detokenizes the response before returning it.