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
  • General
  • JSON
  • Property
  • Advanced
  • Property expansion
  • File inclusion
  1. Configuration reference

Terms and abbreviations

Lingua franca of Fortified configuration

PreviousIntroductionNextProperty expansion

General

JSON

JavaScript Object Notation

JSON is a lightweight data-interchange format. It is easy for humans to read and write. It is easy for machines to parse and generate. It is based on a subset of the JavaScript Programming Language Standard ECMA-262 3rd Edition - December 1999. JSON is a text format that is completely language independent but uses conventions that are familiar to programmers of the C-family of languages, including C, C++, C#, Java, JavaScript, Perl, Python, and many others. These properties make JSON an ideal data-interchange language.

See more:

Property

A property is a name-value pair. Property names are always strings ("..."), values can be of any JSON type.

In JSON a property looks like this:

"property_name": <property-value>

Properties MUST be defined inside an object and separated with comma (,). Objects are defined using curly brackets ({}):

{
  "property_name": <property-value>
}

Property values can be of the following types:

  • string ("string value")

  • number (1, 99, 765474, 3.14)

  • boolean (true, false)

  • object ({})

  • array ([])

{
    "str": "string property",
    "int": 79,
    "float": 3.14,
    "bool": true,
    "obj": {
        "object_property": "another string value"
    },
    "arr": [
        "first array element",
        "second array element"
    ] 
}

Objects and arrays can be nested (an object can contain a property with a value of type array that contain objects).

Advanced

Property expansion

Property expansion means replacing a property value, or parts of a value, with the value of another property. The expression is the path to the property.

{
    "first_property": "first value",
    "second_property": "${first_property}"
}

File inclusion

Configuration supports inclusion of files to enable modularisation. Only files of type JSON (with file extension .json) containing an object or an array can be included.

An inclusion looks like this:

"included_property": "@include:path/to/file.json"

Inclusion will replace the property value with the content of the included file (JSON object or array).

Path to included file can be absolute or relative. Relative path are resolved against the directory of the including file.

For more information and details, see:

For more information and details, see:

https://www.json.org/
Property expansion
File inclusion