ADUCID 4.x

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== ADUCID Server Side Components ======
==== AIM web server ====
This component serves as a communications interface.

==== AIM application ====
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.

The AIM application (simply refferred to as AIM) is controlled by the target application using the R4 interface. Using this interface, it also provides services for working with user data.

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.

==== ADUCID Binder ====
This core component is responsible for seamless authentication.

It takes care about connection between AIM application, PEIG and AIM web server components.
(activated by HTTP status 401) 

When PEIG - AIM communication is complete, the Binder informs the AIM web server and sends the result including additional information like [[concepts:03-multi-factor|PersonalCode]] or [[concepts:02-identity-proofing|Identity proofing status]].

The Binder is also used in transactions, VPN etc.

==== Admin applications ====
See [[settings-mgmt:02-management-apps|Management Applications]] how to configure ADUCID Server side product.

ADUCID 4.x

User Tools

Site Tools

Page Tools