Differences

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

Link to this comparison view

developers:advanced-integration:existing-applications [2016/10/26 07:48] (current)
Line 1: Line 1:
 +====== Integration and changes in existing applications ======
 +
 +This chapter describes two methods of integration with existing applications. Since most applications require linking the electronic identity to a user profile, this structure must persist somewhere. ADUCID thus supports two integration scenarios:
 +
 +  - The link is stored in the ADUCID database
 +  - The link is stored in the integrating application’s database
 +
 +Individual integration approaches are covered in chapters below.
 +
 +===== The link is stored in the ADUCID database =====
 +
 +Each application can own a set of attributes (user attribute set) in ADUCID, and store any information in them (so-called directory personal objects). In this integration scenario, the primary key of the integrating application user is stored in the set of attributes. After storing this information,​ the AIMexecutePersonalObject command is used with the R4 interface’s write method.
 +
 +After successful authentication,​ the application can read the set of attributes by calling the AIMexecutePersonalObject command with the read method, and pair the primary key with the user in the user's database.
 +
 +To create a set of attributes for the given application and for enforcing uniqueness of the primary key, it is necessary to contact the ADUCID administrator (see “ADUCIDServerKit Administration Guide”).
 +
 +The integration scenario is schematically illustrated in the following figure.
 +
 +{{:​developers:​advanced-integration:​integration-without-modification-app-db.png?​nolink&​475x420}}
 +
 +=== Integration without modification of the application database ===
 +
 +===== The link is stored in the integrating application’s database =====
 +
 +Each identity has a unique identifier within the ADUCID framework (so-called User directory index - UDI). In this scenario, the application has to save this identifier at the user. The UDI attribute is available after successful authentication by calling the AIMgetPSLAttributes command of the R4 interface.
 +
 +The integration scenario is schematically illustrated in the following figure.
 +
 +{{:​developers:​advanced-integration:​integration-without-modification-aim-db.png?​nolink&​475x403}}
 +
 +=== Integration without modification of the AIM database ===
 +
  
  • developers/advanced-integration/existing-applications.txt
  • Last modified: 2016/10/26 07:48
  • (external edit)