Differences

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

Link to this comparison view

Both sides previous revision Previous revision
concepts:binding [2019/08/22 11:09]
mpospisek
concepts:binding [2019/11/11 22:30] (current)
mpospisek
Line 7: Line 7:
 The following binding types are currently designed: The following binding types are currently designed:
  
-  * Aapplication binding using PEIG on the same host that the application client is runningApp-PEIG communication uses http redirect to local host port 44240 and A1R (application,​ one device, redirect). +| Name | Description | Communication | 
-  ​* ​Bapplication binding using PEIG on the same host that the application client is runningApp-PEIG communication uses URI schema (Android) and A1U (application,​ one device, URI). +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). ​| 
-  Capplication binding using PEIG on a different host than the application client is runningApp-PEIG communication uses QR code and A2Q (application,​ two devices, QR). +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).  ​
-  ​* ​D1application 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 (switched-off PEIG (red button)). The host with the target application includes ADUCID client software (PEIG). App-PP communication uses RA, PP-PEIG communication uses QR code and A2RQ (application,​ two devices, redirect, QR). +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).            | 
-  ​* ​D2application 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). +D1 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 (switched-off PEIG (red button)). The host with the target application includes ADUCID client software (PEIG). App-PP communication uses RA, PP-PEIG communication uses QR code and A2RQ (application,​ two devices, redirect, QR). | 
-  ​* ​ETLS binding using PEIG on the same host as the application client is runningTLS-PEIG communication uses internal call with URI (beta functionality—not supported in ADUCID 3.1) —T1U (TLS, one device, URI). +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). | 
-  ​* ​FTLS binding using PEIG on a different host than the application client is runningTLS-PEIG communication uses QR code (beta functionality — not supported in ADUCID 3.1) — T2Q (TLS, two devices, QR). +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). | 
-  ​* ​GTLS 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)+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).  | 
 +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)   |
  
 PEIG (PP) evaluates information about the communication path used (input from the application),​ and then transfers the information to AIM by specific binding communication over the R3 interface. PEIG (PP) evaluates information about the communication path used (input from the application),​ and then transfers the information to AIM by specific binding communication over the R3 interface.
  • concepts/binding.1566472158.txt.gz
  • Last modified: 2019/08/22 11:09
  • by mpospisek