API calls when Basic Authentication is Disabled is Inconsistent

XMLWordPrintable

    • Type: Suggestion
    • Resolution: Unresolved
    • None
    • Component/s: REST API
    • None
    • 1

      Issue Summary

      When an API call using Basic authentication is sent to jira, and the authentication method is disabled, the server returns a different error message depending on the API endpoint targeted.

      Steps to Reproduce

      1. In Jira, navigate to Settings > System > Authentication Methods
      2. Disable the feature "Allow basic authentication for API calls"
      3. Fire an API call to Jira using Basic Authentication
      4. Fire a second API call to an internal endpoint

      Expected Results

      A consistent error, like this one below

      {"message":"Basic Authentication has been disabled on this instance."} 

      is returned for all API calls to Jira when Basic Authentication is Disabled

      Actual Results

      The error message changes depending on the API endpoint used in the API call with Basic Authentication.

      For example, if you hit: /rest/issueNav/1/issueTable, Jira responds with:

      {"errorMessages":["The value '{project}' does not exist for the field 'project'."],"errors":{}}%

      Workaround

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

            Assignee:
            Unassigned
            Reporter:
            Patrick Turbett
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: