About Server Plug-Ins

A server plug-in is a third-party component added to ActivID CMS to support functionality on the server side. ActivID CMS calls enrollment plug-ins each time a user attribute is set or retrieved (this corresponds to when calls are made to the setAttributes and getAttributes functions of the Generic Plug-In SPI A Service Provider Interface (SPI) consists of a set of constant definitions and method declarations without implementations and intended to be called or used in a pre-determined generic manner with a set of outputs that meet pre-determined abstract rules and expectations.).

The setAttributes and getAttributes functions use linkParameters, a list of attributes needed by the plug-in to match the identifier of the user inside ActivID CMS with the identifier of the user in the external repository.

Important: If you have configured ActivID CMS to work with more than one type of directory, you may need to specify the directory type by adding a suffix with the directory short name to the .link property key (for example, <plugin name>.link.msft-ad). For details about the directory short names, see Configuring the Generic Plugin.

The attributes are managed by the ActivID CMS portal in the same way as standard LDAP user attributes (attributes that can be displayed in a lookup, updated during issuance, or printed during issuance). For enrollment plug-in attributes, the naming convention is: plug_in_name:attribute_name (for example, GenericPluginSample1:MyUserID).

Topics in this section: