Skip to main content

Triggering operations

To list only accounts, navigate to Manage the System > Resources > Target systems [Manually defined | Automatically discovered] > < Target system > > Test connection > Test list.

To test complete listing as configured on the target system's General information page (account attributes, groups, group attributes, group members):

  1. Open a command prompt in the environment of the Bravura Security Fabric service account, for example:

    runas /user:psadmin cmd

  2. In that command prompt, navigate to the instance's util\ directory.

  3. Run:

    psupdate -list -target <TARGETID>

    where <TARGETID> is the ID of the target system being tested

To test password verify, trigger it from the Front-end (psf) LOGIN screen as part of a passwords.pss authentication chain:

  • Associate at least one account from that target system with a test profile.

  • Place the test target system in the Manage the system > Policies > Authentication List.

To test password resets, change passwords via:

  • Change passwords (pss)

  • Help users (ida)

  • Password Manager service (idpm ), using transparent synchronization. This triggers verifyreset instead of reset.

To test challenge-response configure a challenge-response authentication chain module and trigger it with a test user that exists both in the Bravura Security Fabric database and in the two-factor target system (RSA, DUO, RADIUS)

Other operations like account provisioning, adding accounts to groups, moving account context (from one OU to another) need to be triggered as part of the configured workflow.

The methods described above can generate errors from other product modules, services, scripting and other automation, like workflow configuration, so it is not testing only the connector.

In this section: