Below, you find information to set up Twitter as an identity provider and our SAML SSO apps for Atlassian Data Center and Server products. If you need our help or have questions, you can contact us via our helpdesk or book a free screen share session at https://resolution.de/go/calendly.
Limitations
- During login, Twitter will always ask permission to share the data with your Atlassian DC/Server product. This cannot be turned off, and users must click "Accept" every time during login.
- 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 guides.
In the meantime, the email will be set to "not-existing@example.org" for new users.
Step-by-Step Guides
- Twitter with Just-in-Time Provisioning
Setting up authentication and using Just-in-Time Provisioning to create/update user Accounts during login. - Twitter with Manual Provisioning
Setting up authentication for users that already exist in the Atlassian product.
Which Step-by-Step Guide should you pick?
Depending on your Atlassian Data Center or Server product, you can choose from different user provisioning models. We recommend using Just-In-Time provisioning since it automatically creates users when they log in.
In general, for Atlassian we support the following ways for user provisioning:
- Just in Time Provisioning allows you to create and update users on-the-fly when they log in.
- For Manual User Management, the administrator has to create and update users on your Atlassian Data Center or Server product by hand.
We do not recommend it. See our article for Manual User Management.
| Model/Function | Admin Effort | Pros and Cons |
|---|---|---|
| Just in Time Provisioning | Low |
|
| Manual User Management | High |
|
