Using Smart-Proxy

Disclaimer
Communication with the App Server is implemented in the sample code for demonstration and POC purposes only. It does not include handling of errors and must not be used as-is in the production code.

This chapter specifies use cases for the following scenarios:

  • Password Protection – uses mix of simple and smart endpoints
  • Digital Signature – uses smart entry points only

Smart Entry Point Processing Paradigm

Each request that uses a smart entry point triggers a three-step session that contains:

  1. Create – opens CoTClosedCrypto-of-Things (CoT) - Unbound's CoT ensures that your apps are secure regardless of the security posture of the device on which they’re deployed. session and prepares data for its use that is divided into two parts:
    • Request – contains data required to perform the operation.
    • Context – contains the Unbound Crypto-of-Things SDK data that is carried from step to step. The application is responsible for providing it to the Unbound Crypto-of-Things SDK in steps #2 and #3.
  2. Update – processes the data received in response from the server in the context created by Step #1.

    Note
    This step may be performed several times, depending on the functionality provided by the smart endpoint

  3. Finalize – performs functions required before closing the session, and closes it and returns the result.