Forum Discussion
Jira SSO Logout Loop and UI Issues Across Plugin Versions
One important support-boundary check comes first: Microsoft’s current “JIRA SAML SSO by Microsoft” tutorial carries a May 1, 2026 deprecation notice and directs customers to a supported Atlassian SAML integration. I would confirm the exact installed add-on identity before selecting another version.
Your trace distinguishes local Jira logout from identity-provider logout. If the plugin’s SAML logout endpoint is never invoked, enabling Single Signout in its settings does not prove a SAML logout exchange occurred. Successful Entra authentication also does not prove Jira retained the resulting application session.
I cannot substantiate a confirmed defect, UI fix, or recommended 1.1.11/1.3.7/2.0.7 combination for JSM 10.3.26 from Microsoft’s documentation.
Provide Microsoft’s integration support with the exact add-on identifier, Atlassian’s findings, and a sanitized SAML/redirect trace. In staging, evaluate the supported replacement and test forced login, logout, and session persistence together. Retain both security requirements as acceptance criteria rather than relying on disabling forced login.