• Airlock Secure Access Hub
  • About this document
  • About Airlock IAM
  • IAM 8.4 release notes
  • Security best practices
  • Installation and upgrade
  • Operation
  • Initial configuration
  • Configuration management
  • Authentication
    • Interaction models
    • Authentication methods
    • Remember-Me
    • Step-Up authentication
    • Risk-based authentication
    • Failed logins and temp locking
    • Username transformation
    • Maintenance messages
      • Management
      • Examples in the Loginapp
      • Usage and limitations
      • Locations
    • User representation
    • Events and notifications
    • Login from new device
    • Actions on log out
  • 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. Authentication
  2. Maintenance messages
  3. Examples in the Loginapp

Maintenance messages examples in the Loginapp

Before the login page is displayed, the Loginapp automatically checks for currently valid and active maintenance messages. If there is at least one such message, it is displayed.

Example 1 - message marked with System available:

Example 2 - message marked with System not available: