ADUCID 4.x

User Tools

Site Tools

Trace:
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
documentation:architecture [2018/06/26 14:00]
tjotov 		documentation:architecture [2019/08/01 09:38]
tjotov removed
Line 28: Line 28:
  
 ==== SQL database ==== ==== SQL database ====
-SQL database is used to store ADUCID identites, events and licensing logs. The default SQL DB is Postgress but can be replaced with any JPA compatible DB.+SQL database is used to store ADUCID identites, events and licensing logs. The default SQL DB is PostgreSQL but can be replaced with any JPA compatible DB.
  
 ==== Admin applications ==== ==== Admin applications ====
Line 61: Line 61:
   * Integrated using PEIG API   * Integrated using PEIG API
   * Low level R2 is implemented as UNIX Socket or Windows Pipe   * Low level R2 is implemented as UNIX Socket or Windows Pipe
 +
 +On Windows and OS X PEIG R2 can be called using auxiliary application PEIG which acceps RUI as an arguments and sends it via Unix socket / Windows pipe
  
 ==== R3 ==== ==== R3 ====
Line 70: Line 72:
 R4 is interface between server application and AIM. Like R3 it uses http (or https) transport and SOAP protocol. R4 is interface between server application and AIM. Like R3 it uses http (or https) transport and SOAP protocol.
  
-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 Platform SDK or ADUCID Client SDK for simplified integration.
- +
- +
- +
-==== R2 ==== +
- +
-R2 is an interface between client application and PEIG. This communication can be handled via: +
- +
-  * Uri scheme on mobile phones scheme **aducid** +
-  * Redirect adapter (from browser to Windows / OSX PEIG) is local port 44240 +
-  * Scanning a QR code +
-  * <font 11.0pt/11;;inherit;;inherit>Integrated using Papi</font> +
-==== R3 ==== +
- +
-R3 is an internal interface between PEIG and AIM which uses http transport and SOAP protocol. +
- +
-==== R4 ==== +
- +
-R4 is interface between server application and AIM. Like R3 it uses http (or https) transport and SOAP protocol.+
  
-R4 is “a low level” layer. It is encapsulated in ADUCID WEB SDK or ADUCID JAVA SDK for simplified integration. 
  
 ===== Communication between components ===== ===== Communication between components =====
Line 114: Line 97:
 When the operation is concluded, a random, one-time secret authKey is generated on PEIG<sup>®</sup>  (if successful), which is then transmitted to the client part of the target application along with authId via R2. When the operation is concluded, a random, one-time secret authKey is generated on PEIG<sup>®</sup>  (if successful), which is then transmitted to the client part of the target application along with authId via R2.
  
-<font 11.0pt/11;;inherit;;inherit>The server part uses authId and authKey for further communication with AIM via the R4 interface in order to obtain electronic identity attributes and to work with user data (personal objects). In order for these requests to be carried out successfully, correct values for authId and authKey (one-time secret that was transmitted at the end of a successful operation at the client part of the target application) must be transmitted.</font>+The server part uses authId and authKey for further communication with AIM via the R4 interface in order to obtain electronic identity attributes and to work with user data (personal objects). In order for these requests to be carried out successfully, correct values for authId and authKey (one-time secret that was transmitted at the end of a successful operation at the client part of the target application) must be transmitted.
  
-PEIG finishes its activity by using a return URI. The return URI is transferred from AIM to PEIG during PEIG activity. The return URI is typically [[https://,|https://,]] to activate a registered web browser.+PEIG finishes its activity by using a return URI. Then, depending on scenario, final action is executed (AJAX reload, page refresh, redirect). 
  
  

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki