Skip to end of metadata
Go to start of metadata

Go2Group is pleased to announce the release of Client Certificate Authentication 3.12.


CSV mapping for Basic Mode

Administrators can now configure a comma-separated value (CSV) file with header values and usernames that cannot be found in the application as a last resort.

Table of Contents

CSV mapping “all or none”

In versions before 3.12, if the CSV mapping functionality is users, all applications must exist in the CSV for it to work. This behavior can be noticed when the debug log is enabled:

2018-07-19 10:59:47,257 http-nio-8080-exec-2 INFO [impl.ui.admin.ClientCertService] 6. Certificate Username before CSV: john.doe.1234567890
2018-07-19 10:59:47,258 http-nio-8080-exec-2 INFO [impl.ui.admin.ClientCertService] 7. Certificate Username after CSV:

Version support

In version 3.12, this has been changed whereby if the header value is not found in the header, the code will not return an empty string.

The version matrix has also been updated. Please review the full version matrix below for the supported Atlassian applications.

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, Confluence, Bitbucket Server


  1. Retrieveyour.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 the binary from your Jira Issue
  2. Stop Crowd
  3. Replace the Crowd’s applicationContext-CrowdSecurity.xml with Go2Group’s supplied file. This file can be found at $CROWD_INSTALL/crowd-webapp/WEB-INF/classes (make sure that you save / backup a copy of the file in case you need revert / remove the CCA).
  4. Place the ccacwd-x.x.x.jar in $CROWD_INSTALL/crowd-webapp/WEB-INF/lib
  5. Place the ccacwd.license in $CROWD_INSTALL/crowd-webapp/WEB-INF/classes
  6. Start Crowd