Important Update Effective February 1, 2024!
Due to recent changes in Jira and Confluence, we've made the tough decision to discontinue the OpenID Connect (OIDC)/OAuth app and no longer provide new versions for the newest Jira/Confluence releases as of January 31, 2024.
This is due to some necessary components no longer shipping with Jira/Confluence, which would require some extensive rewrites of the OIDC App.
Important Update! This app will be discontinued soon!
Due to recent changes in Jira, which no longer ships with some components required for our Read Receipts app to run, we've made the tough decision to discontinue the app, as of Februar 5, 2025.
Important Update! This app will be discontinued soon!
We've made the tough business decision to discontinue the app, as of January 11, 2025.
Installing Jira Service Desk after the SAML Single Sign On Add-On
Problem
I am using JIRA. I already have the SAML Single Sign On add-on installed, but after installing the Jira Service Desk application the add-on stops working.
SSO redirection results in an error page and the atlassian-jira log file shows an error like the below:
java.lang.NoClassDefFoundError: com/atlassian/servicedesk/api/organization/OrganizationService at com.resolution.atlasplugins.samlsso.jira.servicedesk.OrganizationAssignerWrapper.create(OrganizationAssignerWrapper.java:71) [?:?] at com.resolution.atlasplugins.samlsso.jira.servicedesk.OrganizationAssignerWrapper.get(OrganizationAssignerWrapper.java:50) [?:?] at com.resolution.atlasplugins.samlsso.jira.userauth.JiraUserPreparator.doPrepareUser(JiraUserPreparator.java:125) [?:?] at com.resolution.atlasplugins.samlsso.userauth.AbstractUserPreparator.prepareUser(AbstractUserPreparator.java:133) [?:?] at com.resolution.atlasplugins.samlsso.userauth.PrincipalProviderImpl.providePrincipal(PrincipalProviderImpl.java:69) [?:?] at com.resolution.atlasplugins.samlsso.userauth.AbstractLoginHandler.login(AbstractLoginHandler.java:51) [?:?]
Solutions
There are two possible solutions to this:
Solution 1
If the "Atlassian Universal Plugin Manager Plugin" is not up to date in your Jira instance, upgrading it to the newest version will make the add-on work again.
Solution 2
If solution 1 doesn't apply to your instance, you need to uninstall the add-on and install it again.
Although the existing add-on configuration isn't deleted when uninstalling, it's recommended to back it up, should you be able to.
You can do that via the System & Support section in the add-on configuration:
You can now uninstall the add-on and install it again. This will fix the problem.
You will now also have access to Jira Service Desk specific settings, which will become visible, if "Enable User Update" is activated.
These will provide more control over actions related to Jira Service Desk organizations.
You can read more about it here: https://wiki.resolution.de/doc/saml-sso/latest/all/further-configuration/organization-assignment