Configuration contexts are used to determine the specific configuration of Airlock IAM based on how IAM is accessed. Using this feature, it is possible for IAM to behave differently, e.g., based on the client or the target URL.
Configuration contexts may be used to avoid duplicating large parts of a configuration and adapt it to a particular context.
It is recommended using configuration contexts sparingly.
Configuration contexts can only be used in the Loginapp, Transaction Approval and API Policy Service.