Skip to main content

Determine the level of product customization

Bravura Security Fabric is a comprehensive suite of products made up of many binaries and scripts, which are designed to work together as a unified identity, privilege, and password management platform.

When troubleshooting or preparing for an upgrade or migration, you must be able to identify if and where the Bravura Security Fabric instance is using stock code versus something customized.

home-version

There are several ways to check for specific versioning changes in your current instance:

  • Look for the version displayed in the default product Web UI footer, as shown above. This is the version of the CGI binary which renders that specific page.

  • Check binary versions and their builds in Windows Explorer by right-clicking the file > Properties > Details. Alternatively you can check version information using the getfileinfo program .

  • Write a complete list of versions for each binary in the product in a text file by running the following in a command prompt from the instance's util directory:

    instdump.exe -binaryversion -outfile binversions.txt

    See instdump for more usage information.

    • For even more details such as file description which includes who each binary was built for, and information on other files like config and non-binaries, and the CommonFiles required by some of these binaries, use PowerShell from the instance directory. For example:

      dir cgi-bin\, agent\, agent\cmn\, interface\, plugin\, service\, util\, design\, report\, wwwdocs\, C:\Program Files\Common Files\Bravura Security\ | Get-ItemProperty |
                  Format-list -Property * -Force > binversions-verbose.txt

      If the agent directory is in the Global Connector Pack location, replace that location in the cmdlet above.

      Add other locations, or use a subset of the command for a specific troubleshooting task.

  • Check if SQL stored procedures in the backend database are customized by comparing them with the default code listed in the instance's db\functions-mssql. sql.

    Similarly, the default backend SQL database schema is provided in db\dbdefault-mssql.sql.

  • Look for custom product UI skins in design\custom.

    When upgrading to a newer version these may not be used as-is, because the UI changes between versions. However, they are useful to determine what has to be changed.

  • Look for custom components in component\Custom (ignore the samples).

    Configuration for installed components and other parts of the product are in db/extdb.db.

  • Identify custom plugin scripts by modification date in the instance's plugin directory

  • Look for other custom scripts, such as pxnull-itsm.cfg which contains exit trap email notifications, in the instance's script\ directory. The date/timestamp is also useful here for identifying modified scripts.

  • See details of the license currently active on a product application node by running the following in a command prompt from the instance's util directory:

    licviewer ..\license\idmsuite.lic

    See licviewer for more usage information

In this section: