What happens in the integration process when the requested information is already available in the IAM system?

Nothing needs to be integrated: the process ends and hands over to the application connection process, which simply connects the application to the existing IAM data.

The very first question of the process is whether the request can be covered by the existing IAM data stock (vorhandener IAM-Datenbestand). This is the cheapest and most common outcome. If the IAM already receives department, e-mail address and cost centre from the HR system, a new application that needs exactly these attributes does not create any work on the source side at all.

What remains is work on the target side: the application has to be connected, for example through a provisioning connector, a directory lookup or a federation login that passes the attributes as claims. That is a different process with its own steps (access request, attribute mapping, testing), so the data-source process stops here with an exit to it.

This exit is why a well-kept IAM data model pays off: the more broadly useful attributes are already in it, the more requests end at this first diamond.

Go deeper:

• Provisioning (technology): User provisioning (Wikipedia) — how IAM data is pushed to connected applications once it exists.