This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
documentation:architecture [2018/06/26 13:57] tjotov [R1] |
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 | + | SQL database is used to store ADUCID identites, events and licensing logs. The default SQL DB is PostgreSQL |
==== Admin applications ==== | ==== Admin applications ==== | ||
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 | + | |
- | * On Unix R1 can be accessed via | + | |
==== R2 ==== | ==== R2 ==== | ||
Line 60: | 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/ | + | * Integrated using PEIG API |
+ | * 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 | ||
==== R3 ==== | ==== R3 ==== | ||
Line 73: | 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 | + | R4 is “a low level” layer. It is encapsulated in ADUCID WEB Platform |
- | + | ||
- | ==== 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 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/ | + | |
- | + | ||
- | ==== 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 133: | Line 97: | ||
When the operation is concluded, a random, one-time secret authKey is generated on PEIG< | When the operation is concluded, a random, one-time secret authKey is generated on PEIG< | ||
- | <font 11.0pt/ | + | 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, |
- | 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 |