• About
  • Release and support
  • Security best practices
  • Installation and upgrade
  • Operation
  • Initial configuration
  • Configuration management
    • Config automation
    • Config environments
    • Configuration variables
    • Configuration contexts
    • External configuration secrets
    • IAM Config Editor (UI)
      • Plugin trees
      • Plugin overview
      • Plugin properties
      • Flow step plugins in IAM flows
      • Sensitive config values
      • View toggles
      • Configuration validation
      • Loading/saving configurations
      • Configuration activation timeout
      • Configuration activation internals
        • Module filenames
        • Examples of activation state files
  • Authentication
  • Self-services
  • Target applications
  • OAuth and OIDC
  • SAML
  • API access control
  • Flows (Airlock IAM concept)
  • Loginapp Configuration
  • Adminapp Configuration
  • Service Container Configuration
  • Transaction Approval Configuration
  • IAM REST APIs
  • Customizing UIs and texts
  • Third-party licenses
  1. Configuration management
  2. IAM Config Editor (UI)
  3. Configuration activation internals
  4. Module filenames

Module filenames

Each running module writes its own file. The file name isMedusaConfigActivationstate.<module-name>

Example file names:

 
Example
  • MedusaConfigActivationstate.loginapp
  • MedusaConfigActivationstate.adminapp
  • MedusaConfigActivationstate.servicecontainerapp
  • MedusaConfigActivationState.api-policy-service
  • MedusaConfigActivationState.transaction-approval