Configuration contexts

Configuration contexts allow using different configuration values for a (typically small) number of configuration values, depending on the situation or context. 

After reading this page, you may also consider Best practices - Configuration contexts and context retention policy.

• Configuration values may, for example, depend on:
• client IPs (e.g. intranet access vs. internet access).
• the URL the Loginapp was accessed by:
• domain a.iam.com or b.iam.com
• context path /auth/ or /secure/ 
• information from a client certificate (mutual TLS).
• the client's (e.g. browser or mobile app) IP address.

• Configuration contexts are available in:
• JSP-Loginapp
• Loginapp REST API


Configuration contexts are determined on Airlock IAM and not in the browser. The Loginapp REST UI is therefore also supported in terms that configuration context may be determined based on the REST requests sent by the Loginapp REST UI.

• Transaction Approval module
• API Policy Service