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.
What should happen if no transformation applies?
There are several options if no regex or value can be transformed/ replaced:
- Use untransformed values
The values are processed as sent by the identity provider. - Ignore the attribute
The attribute will be ignored and not updated/ saved for this user.
Existing values will not be changed. - Clear the attribute value
Only the attributes that could be transformed are assigned; all other values are removed.
For example, the identity provider sends three groups: "A," "B," and "C." Only "C" is transformed, and "A" and "B" are removed.
If the identity provider sends three groups, "A," "B," and "C," and no transformation applies to them, none will be assigned. - Filter the user
If no transformation rule is applied, the user will be filtered. In the context of SAML SSO, authentication for this user will fail.
In the context of UserSync, the user will not be synced, or the cleanup behaviour will be applied if the user already exists.
The below depicts a User Sync connector's Sync Settings tab with the cleanup behaviour, which is always applied only at the end of a full synchronization.