Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

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
4,467,691
Community Members
 
Community Events
177
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:

java.lang.NullPointerException
	at org.kantega.atlaskerb.KerbConfManager.settings(KerbConfManager.java:493) [?:?]
	at org.kantega.atlaskerb.KerbConfManager.isPreemptiveAuthEnabled(KerbConfManager.java:197) [?:?]
	at org.kantega.atlaskerb.AtlasKerberosFilter.isMappedRequest(AtlasKerberosFilter.java:342) [?:?]
	at org.kantega.atlaskerb.AtlasKerberosFilter.doFilter(AtlasKerberosFilter.java:93) [?:?]
	at 

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:

https://confluence.atlassian.com/upm/uninstalling-apps-273875709.html



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

Regards,
Jon Espen
Kantega SSO

0 comments

Comment

Log in or Sign up to comment