documentation:architecture
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
|
documentation:architecture [2018/06/26 11:44] tjotov |
documentation:architecture [2018/06/26 13:57] tjotov [R1] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| {{: | {{: | ||
| - | This chapter describes internal functionality of ADUCID. It is a foundation of[[integration: | + | This chapter describes internal functionality of ADUCID. It is a foundation of [[integration: |
| ===== Target application ===== | ===== Target application ===== | ||
| Line 32: | Line 32: | ||
| ==== Admin applications ==== | ==== Admin applications ==== | ||
| - | ADUCID comes with a set of support applications. All admin applications | + | See [[documentation: |
| - | === PeigAdmin === | ||
| - | PeigAdmin is a PEIG management tool. It also shows statistics and licensing. | ||
| - | |||
| - | === UserAdmin === | ||
| - | |||
| - | UserAdmin is similar to PeigAdmin but also manages proofing data. | ||
| - | |||
| - | === SecAdmin === | ||
| - | SecAdmin is meant to configure security parameters of ADUCID AIM (encryption algorithms, key length, expiration periods etc.) | ||
| ==== Proofing applications ==== | ==== Proofing applications ==== | ||
| Line 53: | Line 44: | ||
| see [[: | see [[: | ||
| - | |||
| - | ===== PEIG proxy QR code ===== | ||
| - | |||
| - | PEIG can act as super secure feature for QR code authentication. In this case PEIG authentication is turned off (but PEIG is running). QR code is not server by AIM-proxy but rather created by PEIG-proxy module. This is one of most secure setups in ADUCID topology (see Binding documentation for details) and definitely secure than displaying QR code using browser. | ||
| ===== Interfaces ===== | ===== Interfaces ===== | ||
| Line 64: | Line 51: | ||
| ==== R1 ==== | ==== R1 ==== | ||
| - | R1 is an application interface handled by customer application itself. In mobile application integration R1 is encapsulated in Papi (PEIG API). | + | R1 is an application interface handled by customer application itself. |
| + | * 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 ==== | ||
Page Tools
