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.
Twitter with Just-in-Time Provisioning
Goal
After completing this setup guide, you will have set up Twitter with Just-in-Time Provisioning and your Atlassian product for the SAML SSO for Atlassian Server or Data Center app. Additionally, you will enable the SSO redirection and test SSO.
If you need help, please reach out to us at https://www.resolution.de/go/support. You can also book a free meeting via https://www.resolution.de/go/calendly.
This will allow any Twitter user to log in to your instance since this will create an account for them. You cannot limit user access from the Twitter side, but it is possible to block users with SAML SSO. Please contact us at https://www.resolution.de/go/support in that case.
With default settings, these users will not be part of an application access group (see Limitations). When granting users application access, please remember any security implications - any Twitter user can use your Atlassian product in this case!
Prerequisites
To use the SAML SSO app for Atlassian Server or Data Center with Azure AD, you need the following:
- A Twitter Developer Account
- A (trial) subscription for the SAML SSO app
- Admin access to your Atlassian product
Limitations
- By default, the newly created users will not have application access because they are not added to a group during login. This can be changed, please see here.
In the context of Jira Service Management, users will be automatically redirected to the service management portal.
- With Twitter OAuth 2.0 API, it is currently not possible to retrieve a user's email address (see here). However, it looks like this might change soon - there already is a checkbox in Twitter's app settings, but that doesn't seem to change anything yet. In case of new developments, we will adjust the guide.
In the meantime, the email will be set to "not-existing@example.org" for new users.
Step-by-Step Setup Guide
Install the SAML SSO App
In your Atlassian product, open the in-product marketplace as described in the Atlassian documentation.
Search for "resolution saml" and click "Install" for SAML Single Sign On (SSO) by resolution Reichert Network Solutions GmbH.
After the installation is complete, click Manage Apps/Addons.
Configure SAML SSO
After you clicked "Configure", the Wizard will be triggered. If not, or if you want to add another Identity Prover (IdP) to your existing configuration, click on "+ Add IdP". This guide assumes, that there is no IdP configured.
The Wizard greets you with information, click on "Add new IdP" to proceed.
Choose Twitter for your Identity Provider and click Next.
Copy the Callback URL and keep it ready for the next step. Click Next.
Go to https://developer.twitter.com/en/portal/dashboard and log in with your Twitter Dev account.
Click + Create Project. (In case of an already existing project, steps may vary a little.)
Enter a project name, then a use case, give it a project description
Now, we must set up an app. Give it a name. You can Ignore the "Keys & Tokens" page.
Next, user authentication must be set up. Click Set up to continue.
For the App permissions, select Read (SAML SSO only needs the profile information and will not read your tweets).
For the Type of App, choose Native App. 
For App info, add the Callback URI from the wizard, and for Website URL, enter your base URL. Click Save.
Next, copy the Client ID and Client Secret to a text editor of your choice.
Add the Client ID and Client Secret. Click Done.
Click Save to save the configuration.
To set up Just-In-Time provisioning, scroll down to User Creation and Update from UserSync-Connector.
Click Create and Setup Just-In-Time Connector.
Afterward, Save the configuration to make the change permanent. Now, when a user logs in, the user is created and/or updated.
That's it! When users log in, their accounts will be created and updated during login.