• Airlock Secure Access Hub
  • About this document
  • About Airlock IAM
  • IAM 8.3 release notes
  • Security best practices
  • Installation and upgrade
  • Operation
  • Initial configuration
  • Configuration management
  • 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
    • Transaction approval REST API
      • Flow selection
      • User identifying step
      • Param. step and message providers
      • Auth token and AuthTokenID usage
      • Approval steps
      • Message provider config
        • Airlock 2FA message provider
        • mTAN message provider
        • Cronto Message Provider
        • mTAN message example
      • Authn. of delegating entity
      • Transaction approval with Airlock 2FA
      • Transaction with mTAN
      • Transaction with Cronto Push
    • Customizing text elements
    • Cronto message custom formatting
  • IAM REST APIs
  • Customizing UIs and texts
  • Third-party licenses
  1. Transaction Approval Configuration
  2. Transaction approval REST API
  3. Message provider config
  4. mTAN message provider

The mTAN message provider

The configuration of the mTAN message provider consists of the Message Translation Key and the String Resource File (which normally doesn't need to be changed).

Furthermore, the mTAN Message Provider needs a maximum length that the message can have (which depends on the SMS provider):