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

Description

This is a major release with 1 major update. Bitbucket Server is now included as a supported application.

When this app is enabled on Bitbucket, users will not be able to perform Git commands via HTTPS anymore and will be restricted to using SSH protocol to access the actual code


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:

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

JIRA Issues

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