Differences

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

Link to this comparison view

Next revision
Previous revision
concepts:architecture [2019/08/01 09:39]
tjotov created
concepts:architecture [2019/11/12 07:22]
tjotov [Target application]
Line 3: Line 3:
 {{:​documentation:​aducid-architecture-overview.png?​400|}} {{:​documentation:​aducid-architecture-overview.png?​400|}}
  
-This chapter describes internal functionality of ADUCID. ​It is a foundation of [[integration:​start|No-code integration]]+This chapter describes internal functionality of ADUCID.
  
-===== Target application ===== +=== Server part of ADUCID ​===
- +
-Target application is any application that uses ADUCID® services. Examples of such applications include web applications with standard thin client (standard browser), mobile applications with server counterpart,​ classic client-server applications,​ or even universal system tools which are not normally viewed as applications,​ e.g. a VPN system for remote access, Wi-Fi connection, terminal access (e.g. X terminal), etc. +
- +
-From the system point of view, the application consists of a client part and a server part (TA Client and TA Server), which communicate with each other in their own manner via an R1 interface. +
- +
-With [[integration:​start|No-code integration]] all applications are insulated behind AAA Proxy. +
- +
-===== Server part of ADUCID® =====+
  
 The entire server part along with the operating system and all third-party systems required to operate the server part of ADUCID are supplied as complete virtual appliance but can be installed as a set of components. The entire server part along with the operating system and all third-party systems required to operate the server part of ADUCID are supplied as complete virtual appliance but can be installed as a set of components.
 +See [[components:​aim|AIM - ADUCID Server Side Components]]
  
-The server side consists ​of these parts:+=== PEIG  - Client part of ADUCID ===
  
-==== AIM ==== +See [[components:​client|PEIG - Client software]]
-ADUCID<​sup>​®</​sup> ​ Identity Machine – delivers ADUCID<​sup>​®</​sup> ​ server functionality,​ performs all ADUCID<​sup>​®</​sup> ​ operations and provides access to user data stored along with electronic identities in the database.+
  
-AIM is controlled by the target application using the R4 interface. Using this interface, it also provides services for working with user data. +=== Target application ​=== 
- +Target application ​is any application that uses ADUCID® servicesExamples of such applications ​include web applications with standard thin client (standard browser), mobile applications with server counterpart,​ classic client-server ​applications, or even universal system tools which are not normally viewed as applications, e.g. a VPN system for remote access, Wi-Fi connection, terminal access (e.g. X terminal), etc.
-Using the R3 interface, it communicates with the client part of ADUCID<​sup>​®</​sup>​. +
- +
- +
-==== SQL database ==== +
-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 ​==== +
- +
-See [[documentation:​admin-applications|Admin ​applications]] +
- +
- +
-==== Proofing applications ==== +
- +
-See [[documentation:​identity-proofing|Identity proofing]] +
- +
- +
-===== PEIG  - Client part of ADUCID ===== +
- +
-see [[:​documentation:​client|PEIG]]+
  
 +From the system point of view, the application consists of a client part and a server part (TA Client and TA Server), which communicate with each other in their own manner via an R1 interface.
  
 +With [[nocode:​start|No-Code Integration]] all applications are insulated behind AAA Proxy.
 ===== Interfaces ===== ===== Interfaces =====
  
  • concepts/architecture.txt
  • Last modified: 2019/11/12 07:22
  • by tjotov