Skip to main content

Inventory of systems

Carry out a complete inventory of potentially affected systems to determine the location of all Bravura Security Fabric components that need to be upgraded or migrated. The following is an example of items to include, not an exhaustive list:

  • Bravura Security Fabric servers

    • Primary server

    • Replica servers

    • Proxy servers

    Caution

    When upgrading, ensure that the server requirements for the new product version are met on the server. See the latest Server requirements in the Bravura Security Fabric configuration documentation. Attempts to upgrade or patch on under-provisioned servers are likely to fail.

  • Target systems

    • Targets with listeners, such as, Unix, OS/390 mainframe

    • Targets with transparent password synchronization triggers, such as, Windows, LDAP Directory Service, Unix, OS/390, IBM OS/400

  • Systems that have Bravura Security Fabric software components installed on them. Examples include:

    • Bravura Security Fabric API installations

    • Local Kiosk software installed on user workstations and laptops

    • Domain Kiosk software installed on domain netlogon shares, called from domain policies

    • GINA or Credential Provider software installed on user workstations

    • Password expiry client or notification client software installed on domain netlogon shares

    • Password Manager Local Reset Extension installed on user workstations

    • Lotus Notes Extension DLL installed on user workstations

  • Other technologies that support Bravura Security Fabric

    • Network load balancers deployed for high availability and/or redundancy

    • Reverse web proxy servers to expose the user interface to other networks

    • Backup servers for disaster recovery

Client tools

A new version of Bravura Security Fabric may need a newer version of the target system client software installed on the primary node.

As of 9.0, Bravura Security Fabric is completely 64-bit, so it requires any target tools (for example, database clients, SDKs or any software our product loads directly to integrate with targets), to also be installed as 64-bit versions. This means that for fresh installs (including replication migrations), the 64-bit clients must be installed, and for cloned migration, the 32-bit clients must be uninstalled and the 64-bit client installed.

Refer to Connector Pack documentation for details on any targets that require target clients or tools.

In this section: