Description:

We would like to request full support for SSH over HTTPS (Port 443) for the GitHub API within the existing connector setup. Currently, due to firewall restrictions that block Port 22 (the default port for SSH), we are unable to enable API functionality using a single connector configuration, even though the connector is set up with a valid SSH URL and the SSH key points to Port 443.

Problem:

While the workaround of maintaining dual connectors (one for SSH and one for HTTPS) works, it is not optimal for all use cases. The ideal solution would be to fully support SSH over HTTPS (Port 443) within a single connector configuration, making it easier to manage and more efficient in environments with strict network restrictions.

Reference:

GitHub provides a specific guide for this use case, which explains how to configure SSH to use Port 443 instead of the default Port 22. This is the behavior we would like to see supported within Harness.

https://docs.github.com/en/authentication/troubleshooting-ssh/using-ssh-over-the-https-port (GitHub SSH Over HTTPS Guide)

Request:

We request that this feature be implemented, allowing customers to use SSH over Port 443 for GitHub API access without requiring multiple connector configurations.