LogoLogo
HomeIntegrityControlSolutionsManagement Center
3.1.0 - Access
3.1.0 - Access
  • Introduction
  • The Service
    • Overview
    • About this release
      • Release notes
      • Breaking changes
    • Architecture
      • Modules
      • Folder structure
      • Startup
    • Getting started
    • Installation
      • Container
      • Linux
      • Windows
    • Operations
      • Configuration
      • Metrics
      • Health check
      • Logging
        • System logging
        • Event logging
      • SBOM & license material
  • Modules
    • External modules
    • Internal modules
      • SAMLModule
      • OIDC
        • OpenID Configuration endpoint
        • JWKS endpoint
        • Authorization endpoint
        • Token endpoint
          • Authorization code
          • Refresh token
        • User info endpoint
        • Introspection endpoint
        • End session endpoint
  • Configuration reference
    • Introduction
    • Terms and abbreviations
    • Property expansion
    • File inclusion
    • Secrets management
    • Examples
  • Authenticators
    • Introduction
    • Common configuration
    • Web Authenticator API
    • Flow control
      • Selector
      • AuthController
      • SSO Authenticator
      • Chain
      • Impersonate
      • Impersonate With Search
    • Credential validators
      • SITHS eID
        • With QR or "app-switch"
      • BankID
        • On another device
        • On mobile device
      • Freja e-ID
        • With user input
        • With QR or "app-switch"
      • Mobile ID
        • With QR or "app-switch"
      • Header based
        • Certificate
      • Pointsharp Net iD Access server
        • On another device
        • On same device
      • Integrated windows login, IWA
      • User name & password
      • User lookup
      • OTP validator
      • Passkey validator
      • Exposed metrics
      • Test
        • Static SAML
        • No operation
    • Protocol managers
      • SAML
        • SAML IDP
        • SAML SP
        • IDP Discovery Service
      • OIDC
        • Authorization Code Flow
        • Implicit Flow
        • OIDC Relying Party
    • UI
Powered by GitBook
On this page
  1. Configuration reference

Examples

Example configuration snippets

Demo configuration with inclusion and expansion

Assume the following directories/files:

/
+ server/
  + config/
    + config.json
    + includes/
      + globals.json
      + modules/
        + mod01.json
        + mod02.json
+ demo/
  + file01
  + file02  
config/config.json
{
    "globals": "@include:includes/globals.json",
    "modules": "@include:includes/modules"
}
config/includes/globals.json
{
    "demo_dir": "/demo"
}
config/includes/modules/mod01.json
{
    "name": "DemoModule",
    "enabled": true,
    "config": {
        "path": "${globals.demo_dir}/file01"
    }
}
config/includes/modules/mod02.json
{
    "name": "DemoModule",
    "enabled": true,
    "config": {
        "path": "${globals.demo_dir}/file02"
    }
}

When inclusion and expansion is performed, config.json will have the following content:

{
    "globals": {
        "base_dir": "/server"
    },
    "modules": [
        {
            "name": "DemoModule",
            "enabled": true,
            "config": {
                "path": "/demo/file01"
            }
        },
        {
            "name": "DemoModule",
            "enabled": true,
            "config": {
                "path": "/demo/file02"
            }
        }
    ]
}

Note that:

  • globals.json include was expanded to an object

  • modules include was expanded to an array containing each of the JSON files in the directory as elements

  • all expansion expressions (${globals.demo_dir}) are replaced with the property value ("/demo")

PreviousSecrets managementNextIntroduction