Uploaded image for project: 'Confluence Data Center'
  1. Confluence Data Center
  2. CONFSERVER-30220

Redirect for login can break

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Low Low
    • 5.1.5, 5.2.3, 5.3
    • 5.1.5
    • None

      After applying the patch for CONF-30221, login redirects can contain a ${originalurl} parameter, instead of the original URL that requires a login.

      If you have configured all of the below:

      1. allowed anonymous access in global permissions
      2. allowed anonymous view in space permissions
      3. restricted some content in that space so that anonymous cannot view it.

      Then any time a non-logged-in user tries to view the restricted content they will be redirected to a login page normally, but once they are logged in they will be redirected to the site homepage, not their original destination.

      Workaround

      Once the user has logged in, they should manually navigate back to the page they intended to view.

          Form Name

            [CONFSERVER-30220] Redirect for login can break

            Stefan Hett added a comment -

            @matt thanks for the answer. I'c.

            Stefan Hett added a comment - @matt thanks for the answer. I'c.

            Matt Ryall added a comment -

            stefan22 - yes, this issue was found with the change for CONF-30221 before we shipped 5.1.5 and fixed in that version.

            If you're seeing the same behaviour in a more recent version of Confluence, please raise a new ticket and we'll review it.

            Matt Ryall added a comment - stefan22 - yes, this issue was found with the change for CONF-30221 before we shipped 5.1.5 and fixed in that version. If you're seeing the same behaviour in a more recent version of Confluence, please raise a new ticket and we'll review it.

            Stefan Hett added a comment - - edited

            Affected version AND fixed version both 5.1.5? This doesn't sound quite right to me. Or does it mean the issue got introduced during 5.1.5 development and was fixed before 5.1.5 was shipped?

            Stefan Hett added a comment - - edited Affected version AND fixed version both 5.1.5? This doesn't sound quite right to me. Or does it mean the issue got introduced during 5.1.5 development and was fixed before 5.1.5 was shipped?

              richatkins Richard Atkins
              richatkins Richard Atkins
              Affected customers:
              0 This affects my team
              Watchers:
              6 Start watching this issue

                Created:
                Updated:
                Resolved: