components:aim
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
components:aim [2020/03/25 23:34] mpospisek |
components:aim [2020/03/28 09:03] (current) mpospisek ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ====== ADUCID Server Side Components ====== | ====== 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 13: | Line 16: | ||
| This core component is responsible for seamless authentication. | This core component is responsible for seamless authentication. | ||
| - | It is displayed when 401 occurs and solves | + | 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, Binder informs | + | When PEIG - AIM communication is complete, |
| - | Binder also serves for transactions, | + | The Binder |
| ==== Admin applications ==== | ==== Admin applications ==== | ||
| - | See [[settings: | + | See [[settings-mgmt:02-management-apps|Management Applications]] how to configure ADUCID Server side product. |
components/aim.1585179286.txt.gz · Last modified: 2020/03/25 23:34 by mpospisek
Page Tools
