Downloading artifacts

In both cases, the artifactId must be coded in Base 64 URL :

artifactId=dXJuOlNOQVA6QmlnRmlsZT89Y2hh…​

Small artifacts — no Blob Storage

The device must evaluate the value specified in the authentication parameter.

The CERTIFICATE value specifies that the given endpoint ( source ) must be called up by appending the artifactId as the query parameter and using the client certificate for authentication.

GET /v1/artifact?artifactId=<base-64-url-safe-encoded-artifact-id>

Large artifacts — with Blob Storage

The device must evaluate the value specified in the authentication parameter.

The value CERTIFICATE_THEN_NONE specifies that the given endpoint ( source ) must be called up by appending the artifactId as the query parameter and using the client certificate for authentication.

GET /v1/setup-file?artifactId=<base-64-url-safe-encoded-artifact-id>

Response:

To download the contents of the SETUP file, you can define that the endpoint specified in the downloadUrl property of the response body must be called up. This is returned with the first requests.

The THEN_NONE part expresses that no authentication information has to be provided for calling up the second endpoint, since the generated URL contains the authentication information.

GET <download-url> // download artifact content