Documentation Nexus IQ Server 1.16

Our documentation site has moved. For the most current version, please see http://help.sonatype.com

22.6. Component Search REST APIs (v2)

You may reach a point where you would like to search for a particular component that has been identified during a CLM evaluation. In other words, you have already completed an evaluation (more likely you have done several or many evaluations), and either the CLM server has identified, or you have claimed, at least one component in that application.

The likely scenario is that CLM has identified many components across all of your applications. Even more likely, a few of the same components show up in several (maybe all) of your applications. In these instances, the Sonatype CLM Component Search API allows you to both find a particular component, as well as get information back about that component.

This API consists of GET requests, which allow you to retrieve component information such as application ID, application name, report URL, component hash, component coordinates, and perhaps most importantly, it provides the highest threat level of the policy violations (for the found component).

Below, we’ve provided an example of the GET request. We’ve done this using the HTTP client cURL. Of course, you could use any HTTP client tool. Additionally, to help demonstrate use of the API, we’ve broken out the various pieces for this request and provided an example of data that is retrieved.

[Note]

Compared to the other APIs, Component Search is fairly simple. However, you should have some basic information about the component coordinates, as well as the Sonatype CLM stage (e.g. build) where the component was analyzed.

Searching for Components. First, make sure your Sonatype CLM server is started. Also, as we mentioned, you will need to have evaluated at least one application. With those two things completed, let’s take a look at the GET API.

GET /api/v2/search/component

Now, in addition to this, you will need to set the stage, and then add your search parameters. Let’s take a look at stage first.

Stage

Typically the stage represents the development lifecycle of your product. There are four stages that are currently supported. These include:

  • build
  • stage
  • stage-release
  • operate

Entering any of these for the stage ID will pull from that specific stage’s evaluation data.

Next up, you need to set the component search parameters using any combination of these options:

Parameters
  • hash - the component hash (e.g. hash=1234567890)
  • componentIdentifier - this is an object that contains the the coordinates of the component and its format.
  • format - this is the format of the component (e.g. "maven").
  • coordinates - this object contains the name/value pairs for identifying coordinates (e.g. artifactId, groupId, and version).

Now, let’s look at an example. Consider a case where we wanted to find all components within the group ID "tomcat", for any applications evaluated during the build stage.. Using the information above, as well as cURL and an encoded URL, here is what we would have…

curl -u admin:admin123 -X GET "http://localhost:8070/api/v2/search/component?stageId=build&componentIdentifier=%7B%22format%22%3A%22maven%22%2C%22coordinates%22%3A%7B%22groupId%22%3A%22tomcat%22%7D%7D"

Of course the above is an encoded URL, so just for a bit of help, here is what a non-encoded URL would look like. This should help you identify the JSON in the example above.

"http://localhost:8070/api/v2/search/component?stageId=build&componentIdentifier={"format":"maven","coordinates":{"groupId":"tomcat"}}"
Note
Included in our cURL example is the default CLM server location (localhost:8070) as well as the default username and password for the admin account. Your account credentials may vary, but are necessary in order for the request to be processed. The results provided will be filtered based on the permissions of the credentials you use. For example, if you are not included in at least the developer role for an application, no results will be returned for that application. Given this, some results may be obscured.

Alright, so in our case, the API above produced the following results. If you have any tomcat components, you could expect something similar…

{
   "criteria":{
      "stageId":"build",
      "hash":null,
      "componentIdentifier":{
         "format":"maven",
         "coordinates":{
            "groupId":"tomcat"
         }
      }
   },
   "results":[
      {
         "applicationId":"MyApp-1234",
         "applicationName":"My Application 2",
         "reportUrl":"http://localhost:8070/ui/links/application/MyApp-1234/report/c81991938f304f30bc139ea13cf93cd5",
         "hash":"1249e25aebb15358bedd",
         "componentIdentifier":{
            "format":"maven",
            "coordinates":{
               "artifactId":"tomcat-util",
               "classifier":"",
               "extension":"jar",
               "groupId":"tomcat",
               "version":"5.5.23"
            }
         }
[Note]

The data above was formatted to make it a bit more readable.

Using Wildcards. Of course, you may come across instances where you want to produce more results with less specific component details. If this is the case, the Component Search API does support the use of wildcards when searching using the GAV (coordinates).

If you are familiar with the coordinates policy condition, it follows the exact same logic. You can read more on the Coordinates condition in Step Five in the Policy Management chapter.