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.
Handling SAML-message failed: Neither the SAML Response nor the Assertion have a valid signature
Problem:
The SAML SSO app for Atlassian Data Center or Server stops working while configured with AD FS. The following error is thrown:
Handling SAML-message failed: Neither the SAML Response nor the Assertion have a valid signature. com.resolution.samlwrapper.api.exception.MessageReadingException:
Neither the SAML Response nor the Assertion have a valid signature.
Solution:
This message usually occurs if the certificate on ADFS has been renewed but not updated in the plugin.
To fix this:
- Go to the SAML Single Sign On for Atlassian Data Center or Server configuration page
- Click on the Identity Providers tab
- Click the Load button next to the Metadata URL field
- Save the configuration - this reloads the metadata and thus the new certificate
If you have configured the Metadata by pasting the XML:
- Update the XML in the field
- Click Load
- Save the configuration
To fix this for the long term, please mark the checkbox Automatic reload (directly below the metadata URL), then our plugin automatically downloads the metadata every 24 hours.
That would prevent the issue to re-occur if the certificate got changed.