Uploaded image for project: 'Jira Service Management Data Center'
  1. Jira Service Management Data Center
  2. JSDSERVER-3539

Anonymous access to a confluence space doesn't allow service desk customer to view

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Tracked Elsewhere
    • Icon: Low Low
    • None
    • None
    • Knowledge Base
    • None

      NOTE: This bug report is for JIRA Service Desk Server. Using JIRA Service Desk Cloud? See the corresponding bug report.

      I've created a release note which I want to be publicly accessible. I've switched on Anonymous access, and then given anonymous users access to view the pages within my 'release notes' space.

      Now, I can open my release note in a browser where I'm not logged in and can see it. Success!
      BUT, if I'm logged in as a Service Desk customer, visiting the same link gives me a 'Not permitted' page. Surely customers should be able to view this page?

      Atlassian Answers post here: https://answers.atlassian.com/questions/37547733/comments/37547778

            [JSDSERVER-3539] Anonymous access to a confluence space doesn't allow service desk customer to view

            Owen made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2305264 ] New: JAC Bug Workflow v3 [ 3125888 ]
            Status Original: Done [ 10044 ] New: Closed [ 6 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 2059209 ] New: JSD Bug Workflow v5 - TEMP [ 2305264 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 - TEMP [ 2056619 ] New: JSD Bug Workflow v5 [ 2059209 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v5 [ 1956293 ] New: JSD Bug Workflow v5 - TEMP [ 2056619 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v4 [ 1615080 ] New: JSD Bug Workflow v5 [ 1956293 ]
            jonah (Inactive) made changes -
            Description Original: I've created a release note which I want to be publicly accessible. I've switched on Anonymous access, and then given anonymous users access to view the pages within my 'release notes' space.

            Now, I can open my release note in a browser where I'm not logged in and can see it. Success!
            BUT, if I'm logged in as a Service Desk customer, visiting the same link gives me a 'Not permitted' page. Surely customers should be able to view this page?

            Atlassian Answers post here: https://answers.atlassian.com/questions/37547733/comments/37547778             		New: {panel:bgColor=#e7f4fa}
              *NOTE:* This bug report is for *JIRA Service Desk Server*. Using *JIRA Service Desk Cloud*? [See the corresponding bug report|http://jira.atlassian.com/browse/JSDCLOUD-3539].
              {panel}

            I've created a release note which I want to be publicly accessible. I've switched on Anonymous access, and then given anonymous users access to view the pages within my 'release notes' space.

            Now, I can open my release note in a browser where I'm not logged in and can see it. Success!
            BUT, if I'm logged in as a Service Desk customer, visiting the same link gives me a 'Not permitted' page. Surely customers should be able to view this page?

            Atlassian Answers post here: https://answers.atlassian.com/questions/37547733/comments/37547778
            jonah (Inactive) made changes -
            Link New: This issue relates to JSDCLOUD-3539 [ JSDCLOUD-3539 ]
            Katherine Yabut made changes -
            Workflow Original: JSD Bug Workflow v2 [ 1602414 ] New: JSD Bug Workflow v4 [ 1615080 ]
            Owen made changes -
            Workflow Original: JSD Bug Workflow [ 1398490 ] New: JSD Bug Workflow v2 [ 1602414 ]
            Marty (Inactive) made changes -
            Component/s New: Knowledge Base [ 26195 ]

              Unassigned Unassigned
              cf4a4bb09906 Kevin Davies
              Affected customers:
              4 This affects my team
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: