ADUCID 4.x

User Tools

Site Tools

Trace:
concepts:01-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
concepts:01-architecture [2019/11/12 07:13]
tjotov [Target application] 		concepts:01-architecture [2019/11/12 07:21]
tjotov [ADUCID architecture]
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 ===== ===== Target application =====
Line 13: Line 13:
 With [[nocode:start|No-Code Integration]] all applications are insulated behind AAA Proxy. With [[nocode:start|No-Code Integration]] all applications are insulated behind AAA Proxy.
  
-===== Server part of ADUCID® =====+=== 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: 
  
-==== AIM ==== 
-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.+=== PEIG  - Client part of ADUCID ===
  
-Using the R3 interface, it communicates with the client part of ADUCID<sup>®</sup>. +See [[components:client|PEIG - Client software]]
- +
- +
-==== 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]]+
  
  
concepts/01-architecture.txt · Last modified: 2020/03/25 22:30 by mpospisek

Page Tools

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki