Dependencies

The CERT® JIRA Plugins depend on installations of Atlassian JIRA 4.4.x and the Bouncycastle implementation of the Java Cryptocraphy Extension and Java Cryptography Architecture.

Filesystem Setup

All CERT® JIRA Plugins have been coded and tested on a Linux based system. Some initial directory/file setup is required to use either EAH or ATC.

Configuration Directories

  • mkdir -p /etc/certops-jira/atc
  • mkdir -p /etc/certops-jira/eah

Log Files Directories

  • mkdir -p /var/lib/jira/logs
  • chown -R tomcat:tomcat /var/lib/jira/logs

Upgrading

JIRA comes with several outdated JARs, which will prevent the CERT® JIRA Plugins from functioning correctly.

BouncyCastle JARs

The CERT® JIRA Plugins have been tested with BouncyCastle versions 144 and later.

  1. Remove any existing BouncyCastle JARs from the JIRA lib directory. JIRA 3 by default ships with bcprov-jdk14-138.jar
  2. Download the latest BouncyCastle JARs http://bouncycastle.org/latest_releases.html
    • bcprov-jdk16-145.jar
    • bcpg-jdk16-145.jar
    • bcmail-jdk16-145.jar
  3. Store the new BouncyCastle JARs in the JIRA lib directory

JavaMail JARs

The CERT® JIRA Plugins have been tested with JavaMail version 1.4.3.

  1. Remove the old Mail and Activation JARs (activation-1.0.2.jar and javamail-1.3.3.jar)
  2. Download the latest JavaMail JARs from http://java.sun.com/products/javamail/
    • mail.jar
  3. Store the new Mail and Activation JARs in the JIRA lib directory

Override Java's Default Encryption Policy Files

By default, Sun ships Java with a resticted key width for encryption.

  1. Download the unlimited strength policy files (Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 6) from http://www.oracle.com/technetwork/java/javase/downloads/index.html
  2. Follow the README.txt file to upgrade to unlimited key strength