Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Kantega SSO and upgrade to Jira 8 - Important notice

Problem description

Jira 8 contains the Atlassian Platform 5.0. This platform changed the autowire-mode from the deprecated 'auto-detect' to 'constructor'. As a result, older versions of Kantega Single Sign-on will not work at all on Jira 8 because core components relied on setter-injection.

Kantega Single Sign-on made neccesary changes to solve this in version 3.4.7.

If you are unlucky to upgrade to Jira 8 before upgrading Kantega Single Sign-on to 3.4.7 or newer, you will have run into a problem.

How is the problem seen?

You will see something similar to this in the log:

	at org.kantega.atlaskerb.KerbConfManager.settings( [?:?]
	at org.kantega.atlaskerb.KerbConfManager.isPreemptiveAuthEnabled( [?:?]
	at org.kantega.atlaskerb.AtlasKerberosFilter.isMappedRequest( [?:?]
	at org.kantega.atlaskerb.AtlasKerberosFilter.doFilter( [?:?]

And you will also experience that you are not able to log into Jira.

How to solve

Best is if you upgrade Kantega Single Sign-on to 3.4.7 or newer before you upgrade Jira 8.

If you did upgrade to Jira 8 and has no easy way to roll back, you will have to remove Kantega Single Sign-on jar file to start up successfully.

Removal is done by:

  • navigating to: <jira_home>/plugins/installed-plugins
  • and removing plugins containing 'kerberosauth' in name with command rm *kerberosauth*

 After the removal, please restart Jira 8 and install Kantega Single Sign-on latest version. You will keep config after reinstalling.

See also details from Atlassian on how to uninstall apps:

Please reach out to our support team if you struggle with your upgrade.

Jon Espen
Kantega SSO



Log in or Sign up to comment