Differences

This shows you the differences between two versions of the page.

Link to this comparison view

concepts:binding [2019/08/01 09:37]
tjotov created
concepts:binding [2019/08/22 11:09] (current)
mpospisek
Line 7: Line 7:
 The following binding types are currently designed: The following binding types are currently designed:
  
-  * A—application binding using PEIG on the same host that the application client is running. App-PEIG communication uses http redirect to local host port 44240and ​A1R (application,​ one device, redirect).+  * A—application binding using PEIG on the same host that the application client is running. App-PEIG communication uses http redirect to local host port 44240 and A1R (application,​ one device, redirect).
   * B—application binding using PEIG on the same host that the application client is running. App-PEIG communication uses URI schema (Android) and A1U (application,​ one device, URI).   * B—application binding using PEIG on the same host that the application client is running. App-PEIG communication uses URI schema (Android) and A1U (application,​ one device, URI).
   * C—application binding using PEIG on a different host than the application client is running. App-PEIG communication uses QR code and A2Q (application,​ two devices, QR).   * C—application binding using PEIG on a different host than the application client is running. App-PEIG communication uses QR code and A2Q (application,​ two devices, QR).
Line 13: Line 13:
   * D2—application binding using PEIG on a different host than the application client is running (two devices). App-PEIG communication uses a QR code displayed by PP (PEIG sign-in OFF). The host with target application includes ADUCID client software (PEIG). App-PP communication uses URI schema, PP-PEIG communication uses QR code—A2UQ (application,​ two devices, URI, QR).   * D2—application binding using PEIG on a different host than the application client is running (two devices). App-PEIG communication uses a QR code displayed by PP (PEIG sign-in OFF). The host with target application includes ADUCID client software (PEIG). App-PP communication uses URI schema, PP-PEIG communication uses QR code—A2UQ (application,​ two devices, URI, QR).
   * E—TLS binding using PEIG on the same host as the application client is running. TLS-PEIG communication uses internal call with URI (beta functionality—not supported in ADUCID 3.1) —T1U (TLS, one device, URI).   * E—TLS binding using PEIG on the same host as the application client is running. TLS-PEIG communication uses internal call with URI (beta functionality—not supported in ADUCID 3.1) —T1U (TLS, one device, URI).
-  * F—TLS binding using PEIG on a different host than the application client is running. TLS-PEIG communication uses QR code (beta functionality —not supported in ADUCID 3.1) —T2Q (TLS, two devices, QR).+  * F—TLS binding using PEIG on a different host than the application client is running. TLS-PEIG communication uses QR code (beta functionality — not supported in ADUCID 3.1) — T2Q (TLS, two devices, QR).
   * G–TLS binding with PEIG on another host than client of the target application (two devices), communicates with TLS-PEIG using  code displayed by PP. On host with TLS is SW  ADUCID ​ (Peig  - deactivated).Communication TLS-PEIG using QR code – T2Q (TLS, 2device, QR)   * G–TLS binding with PEIG on another host than client of the target application (two devices), communicates with TLS-PEIG using  code displayed by PP. On host with TLS is SW  ADUCID ​ (Peig  - deactivated).Communication TLS-PEIG using QR code – T2Q (TLS, 2device, QR)
  
  • concepts/binding.txt
  • Last modified: 2019/08/22 11:09
  • by mpospisek