• 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
  • Self-services
  • Target applications
  • OAuth and OIDC
  • SAML
  • API access control
  • Flows (Airlock IAM concept)
  • Loginapp Configuration
    • Loginapp REST API
    • Loginapp UI
    • One-Shot authentication
    • OAuth / OIDC
      • OAuth AS/OP Configuration
        • Grants and flows
        • Dynamic client registration
        • Authentication flows
        • Scope policies and filtering
        • ACR in flows
        • PAR configuration
        • PKCE configuration for IAM as OAuth 2.0/OIDC authorization server
        • Client authentication configuration private_key_jwt
        • Local consent
          • Consent persister configuration
        • Remote consent
        • OIDC session management
        • Certificate-Bound Access Tokens
        • Loginapp UI configuration
        • Non-interactive OIDC authentication
        • Azure AD B2C
        • Sharepoint SE integration
        • Performance Tuning
      • OAuth Client / RP Configuration
    • HTTP Basic Auth access
    • Event notification
  • Adminapp Configuration
  • Service Container Configuration
  • Transaction Approval Configuration
  • IAM REST APIs
  • Customizing UIs and texts
  • Third-party licenses
  1. Loginapp Configuration
  2. OAuth / OIDC
  3. OAuth AS/OP Configuration
  4. Local consent

Local consent configuration

OAuth 2.0 AS configuration

  1. Go to:
    Loginapp >> OAuth 2.0/OIDC Authorization Servers >> {{AS-Id}} >> OAuth 2.0 Grants/OIDC Flows >> OAuth 2.0 Grants/OIDC Flows
  2. Go to:
    OAuth 2.0 Authorization Code Grant OR OIDC Authorization Code / Hybrid Flow
  3. Go to:
    Section User Interface
  4. Create an OAuth 2.0 Local Consent plugin.
  5. The AS is configured to provide scope information and expect user consent.

Authentication Flow configuration

  1. Go to:
    Loginapp >> Applications and Authentication >> a target application >> Authentication Flow
  2. Add an OAuth 2.0 Consent Step to the list of Steps
  3. The authentication flow contains an interactive step that allows the user to choose which requested scopes are to be granted.

Loginapp UI configuration

  1. Go to:
    Loginapp >> UI Settings >> Authentication UIs >> {{Flow UIs}}
  2. A flow UI for the target application is already configured. The default Loginapp UI contains the consent step.

Further information and links

Internal links:

  • Remote consent configuration