Skip to main content

JIRA Server (Ticket)

Connector name

pxjira

Connector type

Executable with script

Type (UI field value)

JIRA (Ticket)

Target system versions supported / tested

Bravura Security Fabric uses the pxjira interface program to trigger creations and updates on Jira Server when certain events occur on the Bravura Security Fabric server.

Connector status / support

Customer-Verified

Clients may contact Bravura Security support for assistance with this connector. Troubleshooting and testing must be completed in the client's test environment as Bravura Security does not maintain internal test environments for the associated target system.

Installation / setup

Interface programs are installed in the interface directory.

Modify the sample pxjira.cfg script included in the samples directory and copy it to the \<instance>\script\ directory.

The following sections show you how to configure the event actions interface for Bravura Security Fabric 7.0 or higher by:

  • Preparing the target

  • Setting the target system address in Bravura Security Fabric (version 7.0 and higher)

  • Writing a configuration file for event actions

See also

JIRA Server shows you how to configure Bravura Security Fabric to perform operations on accounts directly managed by JIRA Server by using the agtjira connector.

Preparation

In order to interface with JIRA Server, you must ensure JIRA Server is installed properly and project has been created.

Targeting a JIRA Server

Bravura Security Fabric provides the option of using the target system name in event action fields in the Manage the system (PSA) module or Configure event (ITSM) module, rather than the program name. The security benefit is that all sensitive information (server address, admin credentials) is automatically passed to the program, rather than stored in the .cfg file in plain text.

Add a target system in Bravura Security Fabric (Manage the System > Resources > Target systems) for each JIRA Server to support the event actions interface.

  • Set the Type to JIRA (Ticket) , listed under IT Service Management Systems .

  • Address is the name of the JIRA server or IP address

    {server=<serverName>;}

  • Set the Administrator ID and Password to the login ID and password needed to access a JIRA project.

Once you write a configuration file, you can use the target ID to configure event actions in the Manage the system (PSA) module or Configure event (ITSM) module.

Configuring event actions

To configure an event action to interface with JIRA Server, you must write a configuration file. Modify the pxjira.cfg sample script included in the samples directory and copy it to the \<instance>\script\ directory. If you cannot find the sample file, try re-running setup to modify your installation. Sample files are automatically installed with complete (typical) installations. You can select them in custom installations.

When you configure an event, you enter the program name or, as of Bravura Security Fabric version 7.0, the target ID you set up earlier. In both cases, pxjira looks for the default script with the matching name.

You can write an alternative .cfg file; for example when you have multiple JIRA Server targets. When you configure an event, you specify the file using the -cfg parameter; for example:

  • pxjira.exe -cfg myfile.cfg

    or

  • MYTARGET -cfg myfile.cfg

Requirements

If you do not use a ticket target to configure events, you must define the variables shown in the table below in every JIRA Server script.

Table 1. Required variables for JIRA Server

Variable

Description of the value

adminid

The user ID of a user with permissions to perform all operations that you require.

adminpwd

The password for the above user.

server

The name of the server hosts the JIRA Server.



In this section: