Uploaded image for project: 'Confluence Cloud'
  1. Confluence Cloud
  2. CONFCLOUD-72937

JSM Customers be blocked from accessing a Confluence page after logging in

XMLWordPrintable

      Issue Summary

      When a Confluence space is open to any logged-in user (unlicensed) or anonymous, unlicensed users from Jira Service Management will be able to access its pages without a Confluence license.

      Although, when accessing a page through its direct link and thus being asked to log in, these unlicensed users will face a "<e-mail> doesn't have access to Confluence on <instancename>.atlassian.net" message.

      Steps to Reproduce

      1. Link the Confluence space to the Jira Service Management project and set it to Logged-in users in the settings.
      2. Add a customer user (unlicensed) with a valid Atlassian Account.
      3. Add the same account as a user on the site, but without access to any product, like the screenshot below:
      4. Go to Org Portal -> Products -> User Access Settings -> Approved Domains (There must not be any domain with pre-approved access, especially the domain of the user that you are testing with)
      5. Make sure that the test user is not logged in to any of the Atlassian/confluence sites on the browser where you are testing. So, better try in incognito mode. (Else, you will not be able to replicate the bug, because once the user is logged in to any of the confluence sites, the system will allow the user to enter the KB confluence space without any error.)
      6. Have that user access any page from the space. For example, via direct link.

      Expected Results

      The user should be able to access the page without problems.

      Actual Results

      The user will receive a "<e-mail> doesn't have access to Confluence on <instancename>.atlassian.net" message. Please check the video below for more details:

      Workaround

      There are different workarounds for this scenario:

      • Tap the Log in to another account while presented with the pop-up stating that the user does not have access and enter the same email/account.
      • Access the Jira URL first ("example.atlassian.net" without the "/wiki" context path), which should authenticate the user. Once this is done, access the Confluence URL again. This workaround will only work if you are either a JSM customer or have Jira license.

        1. conf_jsm_customer.mp4
          637 kB
        2. image-2021-10-06-22-24-19-617.png
          image-2021-10-06-22-24-19-617.png
          216 kB
        3. image-2021-12-09-11-52-22-843.png
          image-2021-12-09-11-52-22-843.png
          28 kB
        4. portal_user.png
          portal_user.png
          109 kB
        5. Screen Shot 2021-12-09 at 11.52.41 AM.png
          Screen Shot 2021-12-09 at 11.52.41 AM.png
          234 kB

              45533e943ed1 Chloe Dorward
              gtworkowski Guilherme T (Inactive)
              Votes:
              145 Vote for this issue
              Watchers:
              148 Start watching this issue

                Created:
                Updated:
                Resolved: