User Tools

Site Tools


documentation:architecture

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
Next revision Both sides next revision
documentation:architecture [2018/06/26 13:56]
tjotov
documentation:architecture [2018/06/26 14:00]
tjotov
Line 51: Line 51:
 ==== R1 ==== ==== R1 ====
  
-R1 is an application interface handled by customer application itself. +R1 is an application interface handled by customer application itself. In mobile application integration R1 is encapsulated in PEIG API.
-- Between browser and PEIG it's represented by URI call +
-In mobile application integration R1 is encapsulated in PEIG API+
  
 ==== R2 ==== ==== R2 ====
Line 59: Line 57:
 R2 is an interface between client application and PEIG. This communication can be handled via: R2 is an interface between client application and PEIG. This communication can be handled via:
  
-  * Uri scheme on mobile phones scheme **aducid** +  * URI scheme on mobile phones scheme **aducid**
-  * Redirect adapter (from browser to Windows / OSX PEIG) is local port 44240+
   * Scanning a QR code   * Scanning a QR code
-  * <font 11.0pt/11;;inherit;;inherit>Integrated using Papi</font>+  * Integrated using PEIG API 
 +  * Low level R2 is implemented as UNIX Socket or Windows Pipe
  
 ==== R3 ==== ==== R3 ====
Line 74: Line 72:
 R4 is “a low level” layer. It is encapsulated in ADUCID WEB SDK or ADUCID JAVA SDK for simplified integration. R4 is “a low level” layer. It is encapsulated in ADUCID WEB SDK or ADUCID JAVA SDK for simplified integration.
  
-==== Windows PEIG PC, OSX PEIG ==== 
  
-Windows/ OSX PEIG runs on the same computer as user’s browser. Browser processes AIM-proxy script which calls PEIG Redirect Adapter module on local host port. 
- 
-=== PEIG USB === 
- 
-Windows / OSX PEIG has option to store identity files on a USB. This feature is accessible for every PEIG PC / OSX installation inserting USB disk and preparing it for ADUCID. 
- 
- 
-===== Interfaces ===== 
- 
-ADUCID uses 4 basic interfaces: 
- 
-==== R1 ==== 
- 
-R1 is an application interface handled by customer application itself. In mobile application integration R1 is encapsulated in Papi (PEIG API). 
  
 ==== R2 ==== ==== R2 ====
Line 99: Line 82:
   * Scanning a QR code   * Scanning a QR code
   * <font 11.0pt/11;;inherit;;inherit>Integrated using Papi</font>   * <font 11.0pt/11;;inherit;;inherit>Integrated using Papi</font>
- 
 ==== R3 ==== ==== R3 ====