Relevant versions: This information pertains to Xray version 3.x
Before the new platform, when integrating Xray with Artifactory, one of the parameters which were used to define the Artifactory that Xray is connected to is the Artifactory ID. It was also a mandatory requirement to provide one during the onboarding process.
As compared to its predecessors, when upgrading to Xray version 3.x, you no longer need to use your Artifactory ID as part of the Artifactory integration process. However, there are still several APIs that are used by Xray, which require this ID. For example, the dependency graph API requires a single parameter in its payload: path, but the path must include an artifactory_id to be executed.
Until a permanent fix will be implemented, this article will help you to get it.
Resolution
In case this is a new installation of the platform and the integration between Xray and Artifactory was done after and upgrade to the platform, which means that no artifactory_id was ever used, the artifactory_id will be default.
So, to execute the dependency graph API, the payload will be as follows:
In case this integration was done prior to the upgrade to the platform and you are unsure what was the artifactory_id which was used, you will be able to fetch the information from the Postgres database from the binary_managers table, using the following query:
Before the new platform, when integrating Xray with Artifactory, one of the parameters which were used to define the Artifactory that Xray is connected to is the Artifactory ID. It was also a mandatory requirement to provide one during the onboarding process.
As compared to its predecessors, when upgrading to Xray version 3.x, you no longer need to use your Artifactory ID as part of the Artifactory integration process. However, there are still several APIs that are used by Xray, which require this ID. For example, the dependency graph API requires a single parameter in its payload: path, but the path must include an artifactory_id to be executed.
Until a permanent fix will be implemented, this article will help you to get it.
Resolution
In case this is a new installation of the platform and the integration between Xray and Artifactory was done after and upgrade to the platform, which means that no artifactory_id was ever used, the artifactory_id will be default.
So, to execute the dependency graph API, the payload will be as follows:
'default/repository/path/to/artifact'
In case this integration was done prior to the upgrade to the platform and you are unsure what was the artifactory_id which was used, you will be able to fetch the information from the Postgres database from the binary_managers table, using the following query:
$ SELECT bin_mg_id FROM binary_managers;