User Tools

Site Tools


documentation:advanced:binding:start

Differences

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

Link to this comparison view

Next revision
Previous revision
documentation:advanced:binding:start [2016/11/01 07:53]
127.0.0.1 external edit
documentation:advanced:binding:start [2019/08/01 09:36]
tjotov removed
Line 14: Line 14:
   * 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)
  
 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.