• About
  • Release and support
  • Security best practices
  • Installation and upgrade
  • Operation
  • Initial configuration
  • Configuration management
  • Authentication
  • Self-services
  • Target applications
    • Target application selection
    • Access control (end-users)
    • Securing REST / service APIs
    • Identity propagation
    • Terms and conditions
    • PSD2 support
      • PSD2 implementation
      • NextGenPSD2 implementation
        • Interaction models
        • Configuration
          • Gateway configuration
            • Gateway configuration for bank API calls
            • Gateway configuration for user consent
          • IAM configuration
        • HTTP signature verification
        • TPP authn. with NextGenPSD2
        • Performance measures
      • STET PSD2
      • About tech clients
      • Issuer cert. for PSD2
      • Tech client interceptors
  • 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. Target applications
  2. PSD2 support
  3. NextGenPSD2 implementation
  4. Configuration
  5. Gateway configuration
  6. Gateway configuration for user consent

Gateway configuration for user consent

The user consent application is treated as all other web applications protected by Airlock Gateway and IAM. There are no special PSD2-relevant settings.

Follow the instructions in Airlock Gateway for Airlock IAM configuration.