• 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
  • Adminapp Configuration
    • UI configuration/access options
    • Adminapp REST API
    • User search
      • User search configuration
    • Password management
    • Airlock 2FA configuration
    • FIDO configuration
    • Cronto token controller configuration
    • Digipass OTP configuration
    • Matrix card management
    • Remember-Me configuration
    • Generic token controller
    • User Management Extensions
    • Maintenance messages
    • User-group dependent settings
    • Roles and groups in Adminapp
    • Realm administration
    • Event notification
    • Customizing text elements
    • Log viewer
    • Content security policy (CSP)
  • Service Container Configuration
  • Transaction Approval Configuration
  • IAM REST APIs
  • Customizing UIs and texts
  • Third-party licenses
  1. Adminapp Configuration
  2. User search

User search in Adminapp

The user Search feature in the Adminapp is often used by the helpdesk. To make the search efficient and performant, an administrator can customize the search behavior to align it with the database configuration.

The following screen shows the user search screen as it presents itself to an administrator when the advanced options are shown:

Search options

When opening the Users menu, the advanced options of the user search are hidden and the configured default settings apply. In the advanced options, the administrator can set new default settings to fine-tune the search and meet the requirements.

The following table shows the options that are most relevant to optimize the performance of the user search:

Parameter

Description

Performance Impact

Search in

It is configurable, which context data items are searchable and which will be searched by default.

It is recommended to limit the set of context data searched by default and to support this set of context data with a database index.

Only search words

If enabled, an exact match is required for a result.

If disabled, a substring search is performed for results.

It is recommended to enable these options by default since databases are rather inefficient when substring searches are involved.

Case-insensitive search

If this is enabled case is ignored to determine a match.

It depends on the underlying database if case-insensitive searches can still take advantage of database indices. Enabling this option may have a negative impact on performance.