Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-71733

Plugin Data Storage does not display data

XMLWordPrintable

      Issue Summary

      Even on an upgrade or on a fresh install of Jira 8.12.3, when we to access the > System > Plugin Data Storage page, it doesn't return any plugin information, instead, it brings all plugins name as unknown, table column as '$i.table' and rows as '$i.rows'.

      Steps to Reproduce

      • Fresh install of Jira 8.12.3 or 8.13
      • Upgrade to 8.12.3 or 8.13 version of Jira

      Try to access the > System > Plugin Data Storage page

      Expected Results

      This page expected to have all Jira's plugin information

      Actual Results

      We have these results on the Plugin Data Store page -

      Database Tables
      Plugin Table Rows
      <unknown>
      $i.table
      $i.rows
      <unknown>
      $i.table
      $i.table
      $i.table
      $i.table
      $i.rows
      $i.rows
      $i.rows
      $i.rows
      <unknown>
      $i.table
      $i.rows

      Workaround

      If you need information on the DB tables for the most common Jira apps, please review List of Jira Server AO table names and vendors.

      Otherwise, you can perform these steps to restore the functionality in Jira:

      1. Edit <jira-install-dir>/atlassian-jira/WEB-INF/classes/velocity.properties
      2. Replace the full line containing com.atlassian.activeobjects from the introspector.restrict.packages section with: 
         com.atlassian.activeobjects.ao,\
         com.atlassian.activeobjects.config,\
         com.atlassian.activeobjects.internal,\
         com.atlassian.activeobjects.osgi,\
         com.atlassian.activeobjects.plugin,\
         com.atlassian.activeobjects.servlet,\
         com.atlassian.activeobjects.spring,\
         com.atlassian.activeobjects.util,\ 
      1. Replicate the same change in <jira-install-dir>/atlassian-jira/WEB-INF/classes/velocity-static.properties
      2. Restart Jira

      Bear in mind that these changes were made in order to limit potential template injection vulnerabilities, so there are some security implications to this workaround. You might consider making this change, getting the data you need from the page, and then reverting it and restarting Jira again.

              pprzytarski Pawel Przytarski
              8c7f0d7281aa Artur Moura (Inactive)
              Votes:
              51 Vote for this issue
              Watchers:
              80 Start watching this issue

                Created:
                Updated:
                Resolved: