Context dependent configuration allows 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 9.2.3. Best practices - Configuration contexts and context retention policy.
Examples
Configuration values that depend on:
- ●client IPs (e.g. intranet access vs. internet access).
- ●the URL the Loginapp was accessed (e.g. virtual host A or B; Airlock Gateway (WAF) mapping /auth or /clientcert).
- ●URL of the target application (e.g. different when trying to access application A than B).
Configuration contexts are available in:
- ●Loginapp (JSP)
- ●Loginapp REST API
- ●Transaction Approval module
- ●API Policy Service