Pre-requisites

This section is intended for DevSecOps engineers and CI/CD platform teams responsible for integrating the Lineaje GOS Artifactory Proxy into build pipelines. All examples are based on Jenkins, which is the primary reference integration. The same principles apply to any CI/CD system that can configure a package manager registry URL and inject credentials as environment variables.

Pre-requisites

This section is intended for DevSecOps engineers and CI/CD platform teams responsible for integrating the Lineaje GOS Artifactory Proxy into build pipelines. All examples are based on Jenkins, which is the primary reference integration. The same principles apply to any CI/CD system that can configure a package manager registry URL and inject credentials as environment variables.

• Allowlist the following proxy base URL (enforce mode) to allow automatic handling of all packages. All proxy traffic is routed through a single base hostname.

https://enforce.fortknox.v2.prod.veedna.com

• (Optional) Allowlist repository endpoints. Package-manager-specific paths are appended according to each tool's protocol.

Package Manager	Repository Path	Full Endpoint URL
Maven	/artifactory/gos-all-proxy-maven	https://enforce.fortknox.v2.prod.veedna.com/artifactory/gos-all-proxy-maven
PyPI	/artifactory/api/pypi/gos-all-proxy-python/simple	https://enforce.fortknox.v2.prod.veedna.com/artifactory/api/pypi/gos-all-proxy-python/simple
npm	/artifactory/api/npm/gos-all-proxy-npm	https://enforce.fortknox.v2.prod.veedna.com/artifactory/api/npm/gos-all-proxy-npm

Example artifact request paths (appended to the base URL):

Maven

# Maven — JAR artifact 
https://enforce.fortknox.v2.prod.veedna.com/artifactory/gos-all-proxy-maven/ 
    org/json/json/20230227/json-20230227.jar 

PyPI

npm