ADUCID 4.x

User Tools

Site Tools

Trace:
concepts:04-binding

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
concepts:04-binding [2019/08/22 11:09]
mpospisek 		concepts:04-binding [2020/03/25 23:09] (current)
mpospisek ↷ Page name changed from concepts:binding to concepts:04-binding
Line 1: Line 1:
 ====== ADUCID Binding ====== ====== ADUCID Binding ======
  
-Binding is a new, controlled ADUCID functionality.+Binding is a new, ADUCID-controlled functionality. It is used to protect data channel between client and application.
  
 There are several binding types derived from the use scenarios of the target application, ADUCID means (PEIG types) and technological limits. There are several binding types derived from the use scenarios of the target application, ADUCID means (PEIG types) and technological limits.
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 44240 and A1R (application, one device, redirect). +| Name | Description | Communication | 
-  * 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). +| 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). | 
-  * 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). +| 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).  | 
-  * 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). +| 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).            | 
-  * 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). +| 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). | 
-  * 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). +| 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). | 
-  * 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). +| 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). | 
-  * 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)+| 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)   |
  
 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.
Line 105: Line 106:
 \\ \\
  
 +[<>] 
concepts/04-binding.1566472158.txt.gz · Last modified: 2019/08/22 11:09 by mpospisek

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki