How to resolve issues with Confluence SSO Login causing Page Not Found

Cesar Ramirez 16 Reputation points

Hello, we are using this plugin:

Many users are reporting that when they first login for the day (and say they had the browser open over night), their Confluence session has timed out and requires a relogin.

The issue happens when they click on a link (say in Outlook) to a Confluence page before refreshing the session, they are presented with the standard login screen, but hitting Login With Azure AD, results in the error: InResponseTo of the response does not match the ID of the authentication request. Please try again.


They then try again, but when they are logged in, they are always greeted with Page Not Found. If they click the link again where they originally came from (Outlook), it will direct them to the proper page. While they still can login and it's a few extra clicks, many users are frustrated that this is a daily occurrence.

My hunch is that due to the first error, it for some reason fails the redirect to the page that the user originally wanted to navigate to. If there's anything else I can provide/do to resolve this, that would be great. Thanks!

Edit: We're on Confluence Version 7.6.0 and on the latest version of the plugin that is available for download.

Microsoft Entra ID
Microsoft Entra ID
A Microsoft Entra identity service that provides identity management and access control capabilities. Replaces Azure Active Directory.
20,143 questions
0 comments No comments
{count} vote

2 answers

Sort by: Most helpful
  1. Marilee Turscak-MSFT 35,621 Reputation points Microsoft Employee

    Hi @Cesar Ramirez ,

    Have you tried the solution in this thread which says to make sure the internal and external URLs are the same?

    I have also noticed that others have reported this recently so if the above solution does not work, I will check with the product team to see if anything may have changed.

  2. Landwehr, Karsten 1 Reputation point


    we have the exact same issue.

    For our user the "InResponse" error is not such a big issue but the 404 error after they logged in again is.

    While debugging this I saw that, when the users click on the "Login with Azure AD" button again the payload information regarding the "os_destination" gets changed.

    Here you can see the parameter how it's set when the user sees the "InResponse" error:

    And here you can see the parameter after the user has clicked again on the login button:

    Can you please help at which location this parameter might get changes? On AzureAD site or plugin side?

    Best regards,

    0 comments No comments