Message-ID: <912049344.146.1566112721055.JavaMail.daemon@confluence> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_145_499627456.1566112721054" ------=_Part_145_499627456.1566112721054 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html Upgrading to Jira 8 - important notice. Also relevant for future= releases of other Atlassian products.

Upgrading to Jira 8 - important notice. Also relevant for future re= leases of other Atlassian products.

Problem description

Jira 8 internally upgrades to Atlassian Platform 5.0. This = brings a change of autowire-mode from the deprecated 'auto-detect' to 'cons= tructor'. As a result, older versions of Kantega Single Sign-on wil= l not work at all on Jira 8, because core components like the Atla= sKerbFilter relied on setter-injection and aren't initialized properly unde= r Jira 8. 

Crucially: This core authe= ntication component sits on top of all of Jira when Kantega SSO is installe= d, and when not properly initialized, it becomes impossible to use the appl= ication.

The necessary Jira 8 compatibility fixes were released in Kantega S= ingle Sign-on 3.4.7

If Jira server is upgraded to version 8.x before upgrading Kant= ega Single Sign-on to at least version 3.4.7, you will run into the issue, = preventing Jira from working at all.

2019-07-31: So far Kerberos in Kantega Single Sign-on is not supporting = Java 11. We are working on solving this.

How is the problem seen?

You will see something similar to this in the log:

=09at org.kantega.atlaskerb.KerbConfManager.settings( [=
=09at org.kantega.atlaskerb.KerbConfManager.isPreemptiveAuthEnabled(KerbCon= [?:?]
=09at org.kantega.atlaskerb.AtlasKerberosFilter.isMappedRequest(AtlasKerber= [?:?]
=09at org.kantega.atlaskerb.AtlasKerberosFilter.doFilter(AtlasKerberosFilte= [?:?]

And you will be unable to log into Jira.

How to solve

Ideally upgrade Kantega Single Sign-on to 3.4.7 or newer before= upgrading to Jira 8.

If you did upgrade to Jira 8 with no easy way of rolling back, you will = have to remove the Kantega Single Sign-on jar file manually in order to sta= rt up successfully again.

Removal is done by:

 After the removal, please restart Jira 8 and install Kantega Singl= e Sign-on latest version. You will not lose your configuration by r= einstalling.

See also details from Atlassian on how to unin= stall apps manually/in the absence of UPM:


Future versi= ons of other Atlassian products

Atlassian Platform 5.0 will trickle to other Atlassian products in the n= ear future, so this will be relevant for more than just Jira.

To be clear, the compatible version range of Kantega SSO can be trusted = (KSSO versions before 3.4.7 are not flagged as Jira 8 compatible). The prob= lem is that when upgrading the Atlassian server product, it's possible to i= gnore/postpone add-on updates and so end up with an add-on version that's n= ot compatible with the upgraded server. This is usually not a problem, but = in rare cases like this, it can take the entire application down.