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

OAuth requests made using application links will be processed as unauthorized.

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Low Low
    • None
    • 5.6.0
    • AppLinks
    • None

      The following is being thrown into our Bamboo logs quite frequently

      2015-04-09 13:49:02,457 INFO [http-bio-80-exec-98] [AccessLogFilter] 10.40.32.134 GET http://bamboo.starkey.com/rest/remote-event/1/status 1417666kb
      2015-04-09 13:49:02,644 WARN [http-bio-80-exec-21] [AuthenticatorImpl] No executing user assigned for 2LO requests
      2015-04-09 13:49:02,644 INFO [http-bio-80-exec-21] [AuthenticatorImpl] Authenticated app 'jira:6452512' as user 'null' successfully
      

      This looks similar to FE-5126. Requests coming from JIRA along the app link are coming as "null", which is throwing these warnings. The apps authenticate just fine, but these warnings are thrown frequently ~ every 30 seconds

            [BAM-15834] OAuth requests made using application links will be processed as unauthorized.

            This is kind-of still a thing in 2023, is it?

            We see a Problem with Jira 9.4.8 and Bamboo 9.3.1:

            • In our bamboo only specific groups can login and see things.
            • Jira is connected to bamboo via OAuth with impersonation
            • The HTTP Request from Jira contains an `xoauth_requestor_id`
            • The HTTP Response from Bamboo is a 403 with `message: "No global READ permission"`
            • Restoring visibility for Anonymous Users in Bamboo restores Access via Jira

            As a workaround we changed from "OAuth with Impersonation" to regular "OAuth" which helps, but is merely a workaround because it requires all Users to authorize, one by one.

            Peter Körner added a comment - This is kind-of still a thing in 2023, is it? We see a Problem with Jira 9.4.8 and Bamboo 9.3.1: In our bamboo only specific groups can login and see things. Jira is connected to bamboo via OAuth with impersonation The HTTP Request from Jira contains an `xoauth_requestor_id` The HTTP Response from Bamboo is a 403 with `message: "No global READ permission"` Restoring visibility for Anonymous Users in Bamboo restores Access via Jira As a workaround we changed from "OAuth with Impersonation" to regular "OAuth" which helps, but is merely a workaround because it requires all Users to authorize, one by one.

            We have been facing this issue in 6.9.2 and when we upgraded to 7.2.4 also we are seeing this problem

            Jagadeesh_M added a comment - We have been facing this issue in 6.9.2 and when we upgraded to 7.2.4 also we are seeing this problem

              Unassigned Unassigned
              49612c5cfac6 Robert Nelson
              Affected customers:
              11 This affects my team
              Watchers:
              11 Start watching this issue

                Created:
                Updated: