Skip to main content

Configuring plugins

Bravura Security Fabric includes an extensive plugin architecture that allows you to extend its functionality and customize its interface with other programs. Some built-in plugin programs are distributed with Bravura Security Fabric . You can also write custom plugin programs or scripts. All plugin programs and scripts must be placed in the plugin directory. The programs and scripts use plugin points that you enable when configuring Bravura Security Fabric using the Manage the system (PSA) module.

In general, most plugin points are synchronous. They work in the following way:

  1. An event triggers a CGI program to call the plugin program or script and send it input.

  2. The calling program waits while the plugin program or script executes.

  3. The plugin program or script finishes executing and sends its output to the calling program.

  4. The calling program receives the response from the plugin program or script and then continues.

Filter plugins are an exception to this general rule. They receive “streaming” input from stdin, and output a result to stdout, for each item being filtered. See Filter users and Filter resources for more information about writing filter plugins.

Exit traps differ from plugin points in that all exit traps are asynchronous. That is, the calling program starts the interfaced program and does not wait for a response. See Event actions (exit traps) for more information about exit traps.