eIAM supported federation protocols

eIAM provides the connected web applications and native mobile apps (target applications) with references to electronic identities from internal and external identity providers; the term federation is used for the entirety of the resulting association.

* For an example of an eIAM login in a native mobile app, see and source code for it .

eIAM uses the identity protocols OIDC, SAML2.0 and WS-Federation as federation procedures. Web applications and native mobile apps can thus be connected to eIAM.

It is important to understand that even if an application is integrated with WS-Federation or OIDC, the federation for authenticating the user via eIAM-Web, eIAM-TrustBroker and IdP is always done via the SAML 2.0 protocol.

Functionality of Identity Protocols

The identity protocols define how ICT systems exchange information about users, i.e. identity data and authorisation data. The identity protocols used by eIAM are major standards. Therefore, web applications and native mobile apps are easy to connect to eIAM. OTS (off-the-shelf software) and SaaS (software as a service) are mostly already equipped with it and many libraries are available for development projects.

Federation with SAML2.0

Federation with WS

Federation with OIDC