gravitational / teleport

The easiest, and most secure way to access and protect all of your infrastructure.
https://goteleport.com
GNU Affero General Public License v3.0
17.66k stars 1.76k forks source link

Feature Request: Ability to Assign Fixed Ports for Applications in Teleport Connect #49342

Open vanshiag143 opened 15 hours ago

vanshiag143 commented 15 hours ago

I would like to request a feature enhancement in Teleport Connect that allows assigning fixed ports to each application when creating an App Connection.

Current Behavior:

I have configured Teleport with the following application settings:

    - name: "devnet15-1600-rpc-call"
      uri: "http://95.216.xxx.xxx:1600/"  # Base URL Teleport proxies to  
      public_addr: "[devnet15-1600.teleport.moinet.io](http://devnet15-1600.teleport.moinet.io/)"       
    - name: "devnet14-1600-rpc-call"
      uri: "http://65.109.xxx.xxx:1600/"  # Base URL Teleport proxies to  
      public_addr: "[devnet14-1600.teleport.moinet.io](http://devnet14-1600.teleport.moinet.io/)"
    - name: "devnet14-1601-rpc-call"
      uri: "http://65.109.xxx.xxx:1601/"  # Base URL Teleport proxies to  
      public_addr: "[devnet14-1601.teleport.moinet.io](http://devnet14-1601.teleport.moinet.io/)"

When I open devnet14-1600-rpc-call in Teleport Connect, the App Connection assigns a random port (e.g., Port 62430) for local access, as shown below:

App Connection: Port 62430 Access URL: http://localhost:62430/

Desired Behavior: I would like the ability to specify a static local port for each application in the Teleport configuration. For example:

This setting should apply consistently for everyone who has access to the Teleport instance, ensuring uniform port mapping across all users.

This feature would make it easier to manage and remember local ports, avoid conflicts, and improve usability for scenarios requiring fixed port bindings.