Enable Oracle Wallet authentication for discovery

  • Release version: Australia
  • Updated May 25, 2026
  • 1 minute to read

    • Enable Oracle Wallet authentication to use credentials stored on the target server during Oracle database discovery on UNIX systems.

    Before you begin

    • Verify that the configured Discovery user can connect via SSH to the host.
    • Configure Oracle Wallet on the target server for the Discovery user. For more information, see Using Oracle Wallet authentication for Oracle Discovery on Unix/Linux [KB3059862].
    • Verify that the following applications are up to date:
      • Visibility Content starting with version 6.32.0
      • Discovery and Service Mapping Patterns starting with version 1.31.0
      • For Oracle GLAS discovery: Data Collection for Oracle Global Licensing and Advisory Services starting with version 1.12.0

    Role required: discovery_admin

    About this task

    Oracle Wallet stores database credentials directly on the target server. When the glide.discovery.oracle_wallet_authentication property is set to true, discovery reads credentials from Oracle Wallet instead of from applicative credentials stored on the instance. The property is set to false by default.

    Procedure

    1. In the navigation filter, enter sys_properties.list.
    2. In the Name column, search for glide.discovery.oracle_wallet_authentication.
    3. Select the glide.discovery.oracle_wallet_authentication system property.
    4. In the Value field, enter true.
      To switch back to applicative credentials, set the value to false.
    5. Select Update.

    What to do next

    To apply the changes, run discovery.