Skip to main content

Limitations

  1. In general, user actions require the setting of all fields in a single command.

  2. Concur software does not support listing of users. In order to maintain the integrity and consistency between the Bravura Security Fabric database and Concur users, an intermediary storage target system must exist.

    Examples of intermediary targets:

    • A system that supports listing, such as a Microsoft Active Directory server, and that has a superset of the users containing every user using the Concur service.

    • A basic system acting as the store of the Concur users, such as a file-based ODBC target. Users must be created on both systems simultaneously.

    • A manually managed spreadsheet or list used to import users into Concur.

The output of the intermediary target must be formatted into the correct format. For Bravura Security Fabric 12.0.0 and higher this must be SQLite .db formt. Bravura Security Fabric versions earlier than 12.0.0 use .lst files with KVGroup format . The file should only contain existing and active Concur users. See Listing information from target systems for information about the format.

To use an intermediary target system with Concur:

  1. Configure Bravura Security Fabric to list users on the intermediary target system before the Concur target system, by clicking Maintenance > Auto discovery > Connector execution order . See Configuring parallel listing for more information.

  2. Create a psupdate_list_post script to generate the correctly formatted file for agtconcur before psupdate lists users on the Concur target system. See Controlling auto discovery using scripts for more information.

  1. Since Concur software does not support listing users, user attributes cannot be imported to the database.

  2. Group management is not supported by this target system. Implement user security levels by using different template accounts.

In this section: