Do we really need Kantega SSO, or can we just use Jira's built-in SSO?

[MidnightExe]

Hi everyone,

We're currently using the Kantega SSO app for Jira, but we're only using the basic SSO functionality and syncing with our Active Directory. Since Jira now has built-in SSO capabilities, we're wondering if it's still necessary to keep using Kantega SSO or if we can switch to the built-in solution.

current Jira Version: 10.4.1

Has anyone made this transition or compared the two options?

Thanks in advance!

[Priyanka Khare · Accepted solution]

Hello @MidnightExe 

Since you're on Jira DC 10.4.1, you’ve already got built-in SSO support (via SAML 2.0), which might be enough if you're just doing basic SSO and syncing with AD.

Kantega SSO does offer extra features like support for multiple IdPs, better login/logout handling, and more flexibility with user attributes. But if you’re not using those, the built-in option could work fine, and it might save you on licensing costs too.

Since I have not done it myself I would recommend testing the built-in SSO in a staging setup before switching, just to be sure.

Hope that helps!

[MidnightExe]

Hei @Priyanka Khare thank you for your information and help in this topic! WIll try that with my team.

[Jason Bullock]

@MidnightExe were you able to get it functioning? I am attempting the same thing and following the documentation is not helping. Crowd SSO 2.0 | Crowd Data Center 6.3 | Atlassian Documentation

[MidnightExe]

Hei @Jason Bullock no, we did not perform the change yet. We will in the future. For now we are focusing on creating plans on how to change from Atlassian data center to alternatives.