Installing Lockpoint

Note: This documentation is for an older version of Lockpoint.



Here's an admin-level overview of getting your teams going with Cenote Lockpoint.

  1. Make sure your Confluence instance meets the system requirements.
  2. Install the Cenote Lockpoint add-on in your Confluence instance as you would any standard Confluence add-on.
  3. Continue with configuring Lockpoint to match your specific processes for teams and Confluence spaces.

You're done!

Installing Lockpoint

Lockpoint can be downloaded automatically from within the Confluence Add-On Manager. Alternatively, you may download the JAR and upload it to your Confluence installation manually.

After downloading through the in-application add-on manager (or after uploading the JAR), Cenote Lockpoint automatically installs and configures itself. Once the add-on is installed, you can access the licensing page by clicking on the "Configuration" link on the add-on page, or else by manually navigating to the "Cenote Lockpoint" link in the administration menu.

Getting an Evaluation License

If you install Lockpoint directly from the Add-On Manager, you should be automatically prompted to obtain a trial license. If you installed Lockpoint some other way, you can go to the Lockpoint page on the Atlassian Marketplace and click "Try it free" to generate a new 30-day evaluation license.

Confluence Data Center Installation

Cenote Lockpoint 1.6 and above is designed and fully tested to work with Confluence Data Center on Confluence 5.6 or above, subject to meeting the relevant system requirements.

With Confluence Data Center, there are no special installation requirements. Lockpoint may be installed, enabled, disabled and used like any other add-on.

Legacy Confluence Clustered Installation

For legacy Confluence Clustered on Confluence 5.4 or below, you must follow a number of precautions in order to use Lockpoint. In addition, legacy Confluence Clustered is supported only by Lockpoint 1.5.5 and earlier.

Lockpoint relies heavily on the Confluence plugin framework to install and operate correctly. For legacy Confluence Clustered installations, a number of bugs in the Confluence plugin controller (such as CONFSERVER-9281) may impact Lockpoint operation.

We suggest that you adhere to the two restrictions below to keep your legacy Confluence Clustered installation in good health:

With legacy Confluence Clustered, never use the "Enable" or "Disable" features in the Add-On Manager to enable/disable the Lockpoint add-on. Instead, do a full install or uninstall of the add-on. (This feature is safe to use on Confluence Data Center.)

After installing Lockpoint on a legacy Confluence Clustered system, please shut down and restart each node in the cluster. There is no need to take down the entire cluster for this operation—it is sufficient to shut down and restart one node at a time while the remaining nodes continue to handle the remaining load in the cluster. This restart helps prevent the CONF-9281 issue mentioned above, as well as other issues. (These steps are not required for Confluence Data Center.)