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.
SAML SSO Confluence and Atlassian Companion App
Question
Do we need to configure SAML SSO to work with the Atlassian Companion app?
Answer
There should be no interference between the Atlassian Companion app and our SAML SSO app, having the default Force SSO URLs in our app.
Please take care Atlassian Companion App, cannot handle square brackets in file names.
- [Marketing] Budget-new.xlsx (will not work)
- Marketing Budget-new.xlsx (will work)
Reverse proxy
If you are using a reverse proxy normally the reverse proxy performs a pre-authentication before anything is let through to Atlassian (Confluence as an example). In this case the reverse proxy would have to be configured to allow requests from the following URLs.
<base-url>/rest/token-auth/api/*
<base-url>/download/token-auth/attachments/*
<base-url>/plugins/servlet/imgFilter*
<base-url>/rest/analytics/1.0/publish/bulk (only necessary if you have opted in to data collection)
Please have a look at the official Atlassian article if the URLs have been updated: