eIAM APIs

The use of these APIs with eIAM occurs when you cannot read all information from the authentication token at runtime and you need to synchronise or evaluate data in your business application with eIAM.

API changes are communicated by the BIT 6 months in advance (also within the release notes). With the introduction of a new interface version (Vx), the FOITT supports the current version, the new version and the previous version Vx-1, at most until the next but one service release (exclusively). After that, the Vx-1 version can no longer be used. The customer undertakes to arrange for any necessary work to be carried out on the application as a result of the interface changes and, if necessary, to implement this work on schedule.

Graphic

tbd

Liabilities for the customer

The necessary work on the application in case of interface changes after the eIAM integration MUST be ensured by the customer!

In doing so, the defined interface specifications of eIAM must be adhered to in a binding manner; these are not adapted to the target application. If this leads to an incompatibility between the target and eIAM and the target cannot be adapted (the willingness to do this is sometimes not given by SaaS providers), the connection to eIAM is at risk. Such applications should NOT be procured. If this is nevertheless necessary, the client must have an adapter developed and operated at his expense in the BIT or elsewhere in the sense of an intermediary specialist application (cf. ). Such incompatibility does not automatically lead to an exemption from the eIAM subscription obligation.

APIs supplied by eIAM

  • API eIAM-AMW (API for user- and access management)
  • API eIAM-LDS (LDAP access to directory of users and roles)
  • API eIAM-RDM (adminPortal, Remote delegated management of users and roles)