Uploaded image for project: 'Artifactory Binary Repository'
  1. Artifactory Binary Repository
  2. RTFACT-27066

Xray REST API is returning Bad Credentials error after Artifactory upgrade.

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Done
    • Resolution: Done
    • Affects Version/s: 7.38.0, 7.37.14
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Severity:
      High
    • Location:
      External

      Description

      • Problem description: (Must )
        After upgrading the customer to the latest Artifactory version 7.37.14, the customer started seeing Bad credentials errors on Xray REST APIs when artifactory.override.context.path is set to any value other than artifactory. The error was reproducible using the tokens and basic authentication. 
      • What is the impact to the customer - What are they trying to achieve? where does that bug hurts them? what does it stop them from achieving? (Must )
        The customer was not able to use Xray REST APIs to get their watch list and impacted their day-to-day builds by not scanning their artifacts and failing the builds.
      • What is the expected behavior? (Must )
        The REST API should provide the relevant output instead of bad credentials.
      • Steps to reproduce: (On a clean environment) Must 
      1. Install Artifactory v7.37.14.
      2. Set the property "artifactory.override.context.path=xxx" (any value other than artifactory)
      3. Run any Xray REST API. Example : curl -utestuser:Password -XGET "https://art-url/xray/api/v1/system/user_ping"
      4. Output obtained is {"error":"Bad Credentials"}%  
      • Environment details: 
      • Artifactory/Xray version which the bug was reproduced on (If the bug was reproduced not on the latest major, please test on the latest version as well.) (Must ): 7.37.14, also tested in 7.38.6. With Xray v3.46.0.**
      • DB type & Version (Must ) NA
      • Is this an HA env? if so, how many nodes are used?(Must ) NA
      • Is this On-Prem or SaaS? (Must ) Saas, but it is also reproducible on on-prem environment.
      • Possible workaround: Add the below properties in Artifactory system properties resolved the issue:
        artifactory.context.path=artifactory;
        artifactory.override.context.path=artifactory

        Attachments

          Activity

              People

              Assignee:
              Unassigned
              Reporter:
              shilpak Shilpa Kallaganad
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Sync Status

                  Connection: RTFACT Sync
                  RTMID-27130 -
                  SYNCHRONIZED
                  • Last Sync Date: