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.
Windows Integrated Authentication with Chrome/Firefox
Problem
When doing an SSO login/test with the SAML SSO for Atlassian Data Center or Server app, the AD FS page/dialog prompts to enter username and password for authentication. At this step, the Windows integrated authentication is actually expected to use the logged in windows domain credentials for automated authentication. (With Internet Explorer/Edge it works).
Solution
Applying the following command on an admin powershell on the ADFS Server should solve the authentication problem for Chrome/Firefox:
Set-ADFSProperties -WIASupportedUserAgents (((Get-ADFSProperties).WIASupportedUserAgents)+'Mozilla/5.0')
This essentially adds Chrome/Firefox to the allowed User Agents on AD FS to enable authentication via Windows integrated authentication. That should work with all modern versions of Chrome/Firefox.
Please find more background here: Configure browsers to use Windows Integrated Authentication (WIA) with AD FS