Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-13289

Anonymous view of the Build release tab does not show build details but rather throws errors.

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 5.0
    • None
    • JIRA integration
    • None

    • Bamboo 4.0.1

      Steps to reproduce

      1. Create application between JIRA and Bamboo server as illustrated in http://confluence.atlassian.com/display/JIRA/Integrating+JIRA+with+Bamboo
      2. Configured the Jira project with the permissions Browse Project and View Version Control to Group (Anyone) so that anonymous (not logged in) users can view the project, and view released versions.
      3. Configured the Bamboo project with the permission View set to Anonymous Users.
      4. Login to JIRA and view a released version, the Builds tab correctly displays relevant builds from Bamboo including the details.
      5. Now logout of JIRA and try to view the same release tab related to that project and you will get an error "An error occurred while trying to retrieve the build information".

      Note: Accessing Bamboo anonymously shows the build information which JIRA is restricting.

            [BAM-13289] Anonymous view of the Build release tab does not show build details but rather throws errors.

            Sultan Maiyaki (Inactive) added a comment -

            This issue seem to be fixed in the later versions of JIRA 5.2 and Bamboo 4.4.x as it display a clearer message that:

            Client must be authenticated to access this resource.

            This is replicated using all the authentication methods

            Sultan Maiyaki (Inactive) added a comment - This issue seem to be fixed in the later versions of JIRA 5.2 and Bamboo 4.4.x as it display a clearer message that: Client must be authenticated to access this resource. This is replicated using all the authentication methods

            James Dumay added a comment -

            Hi mdovey,

            Its highly likely that this bug will be fixed when we replace the current JIRA-Bamboo integration with the new one thats due out later this year.

            That said, Ill move this to our internal backlog and see if this is something we can fix easily in our next bug fix sprint.

            Thanks
            James Dumay
            Product Manager

            James Dumay added a comment - Hi mdovey , Its highly likely that this bug will be fixed when we replace the current JIRA-Bamboo integration with the new one thats due out later this year. That said, Ill move this to our internal backlog and see if this is something we can fix easily in our next bug fix sprint. Thanks James Dumay Product Manager

            James Dumay added a comment -

            smaiyaki what kind of application link was used when setting this up? Trusted Apps, OAuth?

            James Dumay added a comment - smaiyaki what kind of application link was used when setting this up? Trusted Apps, OAuth?

            Matthew J. Dovey added a comment -

            I would regards this as a higher priority than minor. This breaks the ability of jira/bamboo being used to allow public/anonymous users the ability to access the history of releases without creating a user account, and is a highly visible bug since it occurs when a jira project is publically viewable. As far as I can tell, there is no workaround to the problem.

            Matthew J. Dovey added a comment - I would regards this as a higher priority than minor. This breaks the ability of jira/bamboo being used to allow public/anonymous users the ability to access the history of releases without creating a user account, and is a highly visible bug since it occurs when a jira project is publically viewable. As far as I can tell, there is no workaround to the problem.

              Unassigned Unassigned
              smaiyaki Sultan Maiyaki (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: