/
Client Certificate Authentication 3.1.2 Release Notes

Client Certificate Authentication 3.1.2 Release Notes

Created by Former user (Deleted)
Last updated: Dec 05, 2017

Go2Group is please to announce the release of Client Certificate Authentication 3.1.2.

Description

This is a major release with 1 major change. We have now included a Basic mode for configuring the CAC application in JIRA, Confluence and Crowd.

The Basic mode allows administrators to convert the CN from ssl_client_s_dn into an Atlassian username by using a drop down select list. For example, C=US/O=U.S. Government/OU=DoD/OU=PKI/OU=ABC/CN=JOHN.RANDOM.DOE.9999999999 can be converted to:

  • john.doe
  • jdoe
  • johndoe
  • 9999999999
  • john.middle.doe

For the existing configuration screen that was introduced in version 3.0, it can be found in the Advance mode tab.

At the moment, version 3.1.x only supports JIRA, Confluence and Crowd. We're working hard to release a version of the solution that would work for the rest of the Atlassian applications.

Download

Users can request for a download (along with the documentation) from our Service Desk at:

Upgrade Guide

In general, if you are coming from a previous version of the solution, users will have to revert the installation procedures to remove the current setup. After that:

JIRA & ConfluenceCrowd
  1. Retrieve your .jar
  2. Head over to the application's UPM
  3. Upload the .jar
  4. Head over to the application's administration screen and look for CCA Authentication Configuration link
  1. Retrieve your .jar
  2. Stop the Crowd instance
  3. Install the .jar into $CROWD_HOME/plugins
    1. If the plugins folder does not exist, create it
  4. Start the Crowd instance
  5. Head over to the application's administration screen and look for CCA Authentication Configuration link

Version Matrix

This page contains the version matrix for the Client Certificate Authenticator solution.

  • If the version is not on the list, it is not supported

  • Goldfinger Holdings assumes that the add-on works because the code compiles against x.y. If it does not work for any x.y.z, please raise a support ticket at our JIRA instance

  • Strikethroughs on the App version(s) means that we do not support that version anymore

Legend:

(question) = Not fully tested or testing in progress

(tick) = Tested version

JIRA

Atlassian Product Version / Application Version

10.x

9.x

8.22.x - 8.13.x

8.12.x -  8.8.x

8.7.x - 8.4.x

8.3.x - 8.1.x

4.0

(tick)

(error)

(error)

(error)

(error)

(error)

3.19.1-6

(error)

(tick)

(tick)

(tick)

(tick)

(tick)

3.19.0

(error)

(tick)

(tick)

(tick)

(error)

(error)

3.18.2 - 3.18.1

(error)

(error)

(tick)

(tick)

(error)

(error)

3.17.2

(error)

(error)

(error)

(error)

(tick)

(error)

3.15.3

(error)

(error)

(error)

(error)

(error)

(tick)

Confluence

Atlassian Product Version / Application Version

8.0-9.03

7.15.x - 7.9.x

7.8.x - 7.5.x

7.4.x - 7.1.x

7.0.x

4.0

(tick)

(error)

(error)

(error)

(error)

3.19.3

(error)

(tick)

(tick)

(tick)

(tick)

3.18.2 - 3.18.1

(error)

(tick)

(tick)

(tick)

(tick)

3.17.2

(error)

(tick)

(tick)

(tick)

(tick)

3.15.3

(error)

(error)

(error)

(error)

(error)

Stash / Bitbucket Server

3.19.0.2

  • This version (3.19.0.2) is only applicable if 3.19.0 cannot be enabled on Bitbucket Server 7.7.x

Atlassian Product Version / Application Version

8.0-9.4.1

7.9.x - 7.7.x

7.6.x - 7.0.x

7.1.x

4.0

(tick)

(error)

(error)

(error)

3.19.0 & 3.19.0.2*

(error)

(tick)

(error)

(error)

3.18.2 - 3.18.1

(error)

(error)

(tick)

(tick)

3.17.2

(error)

(error)

(error)

(error)

Bamboo

Atlassian Product Version / Application Version

9.0.x

8.0.x

7.2.x - 7.0.x

6.10.x

3.19.2

(tick)

(tick)

(tick)

(error)

3.19.0

(error)

(tick)

(tick)

(error)

3.18.2 - 3.18.1

(error)

(error)

(tick)

(error)

3.17.2

(error)

(error)

(error)

(tick)

Crowd

Atlassian Product Version / Application Version

4.0.2

3.19.0

(tick)

3.18.2 - 3.18.1

(tick)

JIRA Issues

You have to be logged on to JIRA to view the issues


type key summary priority status resolution

Unable to locate Jira server for this macro. It may be due to Application Link configuration.