This topic provides settings and permissions for the Nexus Connector.
Nexus Permissions Required
Ensure the connected user account has the following permissions in the Nexus Server.
- Repo: All repositories (Read)
- Nexus UI: Repository Browser
If used as a Docker Repo, the user needs:
- List images and tags
- Pull images
Artifact Type Support
- M - Metadata. This includes Docker image and registry information. For AMI, this means AMI ID-only.
- Blank - Not supported.
|Docker Image(Kubernetes/Helm)||AWS AMI||AWS CodeDeploy||AWS Lambda||JAR||RPM||TAR||WAR||ZIP||PCF||IIS|
Nexus 3 Artifact Servers only.
Nexus Artifact Server
The Harness Nexus Artifact server connects your Harness account to your Nexus artifact resources. It has the following settings.
The unique name for this Connector.
See Tags Reference.
Nexus Repository URL
The URL that you use to connect to your Nexus server. For example,
The Version field in the dialog lists the supported Nexus version, 3.x.
For Nexus 3.x, Harness supports only the Docker repository format as the artifact source.
The username and password for the Nexus account.
The password uses a Harness Encrypted Text secret.
Nexus Artifact Details
The URL you would use in the Docker login to fetch the artifact. This is the same as the domain name and port you use for
docker login hostname:port.
The port you use for
docker login hostname:port. As a best practice, include the scheme and port. For example
https://your-repo:443. If you cannot locate the scheme, you may omit it, for example
For more information, see Docker Repository Configuration and Client Connection and Using Nexus 3 as Your Repository – Part 3: Docker Images from Sonatype.
Name of the repository where the artifact is located.
The name of the artifact you want to deploy. For example,
The repository and artifact path must not begin or end with
Select a Tag from the list.