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.
How to handle Null values in the Email Address user attribute
Problem:
We have the UserSync "Email Address" attribute mapped to a custom IdP attribute which does not always have a value for users, but we want those users to be added to the UserSync directory in our Atlassian product anyway.
We would like UserSync to add/update users regardless of whether ATTR_EMAIL has a value or not.
Solution:
There are two solutions to that problem. The obvious one is to solve it on the IdP level and making sure that the attribute is available for all users.
Another solution is to use our First transformer which will use the first present attribute.
- Go to UserSync and click Edit on the connector. Next, go to the Provisioning Settings tab and scroll down to the Attribute Mapping. Click Edit on the Email row (or any other row with that problem).
- For the Source Type, choose Define a list of attributes ... from the dropdown.
- Add the primary attribute you want to use. You can add as many alternatives as you like. The first available value will be used. You can also apply any transformation from below.
- Click Apply and Save the connector.