This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
components:aim [2019/11/12 07:16] tjotov |
components:aim [2020/03/28 09:03] (current) mpospisek ↷ Links adapted because of a move operation |
||
---|---|---|---|
Line 1: | Line 1: | ||
- | ====== | + | ====== ADUCID Server Side Components ====== |
- | ==== AIM ==== | + | ==== AIM web server ==== |
+ | This component serves as a communications interface. | ||
+ | |||
+ | ==== AIM application | ||
ADUCID< | ADUCID< | ||
- | AIM is controlled by the target application using the R4 interface. Using this interface, it also provides services for working with user data. | + | 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< | Using the R3 interface, it communicates with the client part of ADUCID< | ||
Line 10: | Line 13: | ||
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. | 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 | + | ==== ADUCID Binder |
+ | This core component is responsible for seamless authentication. | ||
- | Sww | + | It takes care about connection between AIM application, |
- | See [[documentation: | + | (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: | ||
+ | |||
+ | The Binder is also used in transactions, | ||
+ | |||
+ | ==== Admin applications ==== | ||
+ | See [[settings-mgmt: | ||
- | ==== Proofing applications ==== | ||
- | See [[documentation: |