Delegate Connection Requirements

Updated 8 months ago by Michael Cretzman

This article lists the permissions and ports that the Harness Delegate requires to access your artifact servers, cloud providers, and verification and security providers.

How does Harness Connect to Providers?

Harness Manager connects to artifact servers, cloud providers, verification providers, and security providers using the Harness Delegate. You download the Harness Delegate from the Harness Manager and install it in your network or VPC.

For information on Harness architecture, see .

The Delegate connects to the Harness Manager only via an outbound HTTPS/WSS connection over port 443. There is no inbound connection from the Harness Manager to the Delegate.

The Delegate and the Harness Manager (via SaaS) establish a Secure WebSocket channel (WebSocket over TLS) to send new Delegate task event notifications (not the tasks themselves) and exchange connection heartbeats. In the case that the WebSocket connection is dropped, the Harness Delegate falls back to outbound-only, polling-based task fetch.

In the Harness Manager, you configure artifact servers, cloud providers, verification, and security providers using your account credentials with those providers. The Delegate uses those credentials when it uses your providers in the Harness deployment, verification, and security processes.

Harness Delegate Connection to Harness Manager

The Delegate runs from within your enterprise network or VPC and only connects to the Harness Manager with a secure outbound HTTPS connection over port 443.

  • HTTPS port 443 outbound from locally-installed delegate to the Harness Manager.
  • HTTPS port 443 from your browser to the Harness Manager.
The Harness Delegate does NOT require root account access, but the Kubernetes, ECS, and Docker Delegates run as root by default. This is to enable the Delegate to install applications using Delegate Profiles (apt-get, etc). If you do not need to install applications using Delegate Profiles, then you can use a non-root account or install the application without the Delegate.

Permissions and Ports for Harness Connections

The following table lists the permissions and ports needed for the Harness Delegate to access artifact servers, cloud providers, verification, and security providers. You configure these settings in the Harness Manager.

  • Artifact servers: The Delegate pulls artifacts and metadata from artifact servers using the account and ports required by the artifact server.
  • Deployments: Most Harness deployments to Virtual Machines (for example, AWS, GCP, Azure, Datacenter) are performed using SSH over port 22. The VPC firewall setting might also require additional open ports for administration, such as HTTP 443.
  • Verifications: The Delegate makes API calls to verification providers using the access keys required by the providers.
  • Security: For security, such as SAML and LDAP, the Delegate uses the account and ports required by the provider, such as a Active Directory domain controller running in a Azure or AWS VPC.
In general, if you are already connecting to your artifact servers, cloud, verification, and security providers from within your network or VPC, and you install the Harness Delegate inside that network or VPC, there is little network or VPC configuration needed. You simply need to specify accounts and ports when configuring Harness to use the providers.


Permissions and Harness Docs

Ports for Delegate Connections to Services

Provider References

Active Directory LDAP

User account in the Active Directory.

HTTPS: 443.

LDAP without SSL: 389.

Secure LDAP (LDAPS): 636.

Users and Groups


General permission: View, Edit and Delete permissions for new applications can be set as part of the default permissions for a custom role.

HTTP: 80

General Permissions

AWS Cloud

IAM user to be able to make API requests to AWS.

Depends on the firewall settings of your VPC, but typically, HTTP: 443.

Creating an IAM User in Your AWS Account

AWS CodeDeploy


HTTPS: 443.

AWS Managed (Predefined) Policies for AWS CodeDeploy


Policy: AmazonEC2FullAccess

HTTP: 80.

HTTP: 443.

TCP: 9090.

Controlling Access to Amazon EC2 Resources


Policy for Elastic Load Balancer, Application Load Balancer, and Elastic Container Service:

Well-known ports: 25, 80, 443, 465, and 587.

Amazon ECS Service Scheduler IAM Role


Policy: AmazonS3ReadOnlyAccess

HTTP: 443.

Creating an IAM User in Your AWS Account


Client (Application) and Tenant (Directory) IDs, and Key.

Windows VMs (WinRM ports): HTTP: 5985, HTTPS: 5986.

Get application ID and authentication key


Username and password for account.

HTTP: 443.

TCP: 8085.

Bamboo permissions


Data Access API Auth Token.

The Bugsnag Data Access API is exposed on the same TCP port as the dashboard, 49080.

Data Access API Authentication


API Key.

HTTPS: 443.

Open Ports

Docker Registry

User permission level.

TCP: 8083.

Permission levels


Access token.

HTTPS: 443.

Access tokens

ELK Elasticsearch

User (Read permission) or Token Header and Token Value.

TCP: 9200.

User authentication

Github Repo

User account: repository owner.

Organization account: read and write.

HTTP: 443.

Permission levels for a user account repository

Repository permission levels for an organization

Google Cloud Platform (GCP)


SSH: 22.

Understanding Roles

JFrog Artifactory

Privileged User: Read permission.

HTTP: 443.

Managing Permissions


Matrix-based: Read permission.

Execute Permission, if jobs are triggered from Workflow.

HTTPS: 443.

Matrix-based security

Kubernetes Cluster

One of the following:

  • Same cluster as kubernetes delegate. Use this option if you installed the Harness delegate in your cluster.
  • Username and password.
  • CA certificate, client certificate, and client key. Key passphrase and key algorithm are optional.
  • For OpenShift: Kubernetes service account token.

Kubernetes Cluster

Depends where the cluster is hosted, such as GCP or AWS.




HTTPS: 443.

Announcing the Search API


Kubernetes service account token.

HTTPS: 443.

Enabling Service Account Authentication

New Relic

API key.

HTTPS: 443.

Access to REST API keys


User account with Repository View Privilege or read for repository.

TCP: 8081.

Nexus Managing Security

Pivotal Cloud Foundry

User account with Admin, Org Manager, or Space Manager role. The user account must be able to update spaces, orgs, and applications.

HTTP: 80 or 443.

Orgs, Spaces, Roles, and Permissions



Depends on where the Prometheus server is hosted. For example, on AWS, port 9090 might be required.




TCP: 25.


User account with Read permissions on eventtypes objects.

TCP: 8089 for API.

Set permissions for objects in a Splunk app

Sumo Logic

User account with access ID and key and query permissions.

HTTPS: 443.

API Authentication


User account in the same Active Directory domain as the Windows instances the connection uses.

HTTP: 5985.

HTTPS: 5986 and 443.

SSH: 22.

Installation and Configuration for Windows Remote Management

How did we do?