ACLI using OAuth web authentication returning unexpected 401 response for calls to Forms REST API endpoints

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • Component/s: Atlassian CLI
    • None
    • 1
    • Severity 3 - Minor

      Issue Summary

      The ACLI is using the wrong URL pattern when calling the Jira Forms API with OAuth 2.0 (3LO) authentication. Specifically, it uses the Basic Auth URL pattern ({{/jira/forms/cloud/

      {cloudId}/...}}) instead of the OAuth URL pattern ({{/ex/jira/{cloudId}

      /forms/...}}), which causes a 401 Unauthorized response.

      Steps to Reproduce

      1. Authenticate via acli jira auth login --web.
      2. Confirm read:jira-work is present in the access token's scope claim.
      3. Call the Forms API endpoint GET https://api.atlassian.com/jira/forms/cloud/<cloud-id>/issue/<work-item-key>/form/<form-ID>/format/answers with headers: Authorization: Bearer <access_token> and observe it results in a 401 error message.

      Expected Results

      ACLI should be using the OAuth URL pattern, which would result in an HTTP 200 result.

      Actual Results

      ACLI is using the Basic Auth URL pattern, which results in calls returning HTTP 401 responses.

      Workaround

      Currently, there is no known workaround for this behavior. A workaround will be added here when available

              Assignee:
              Akash kumar
              Reporter:
              Danieli Barboza
              Votes:
              1 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated: