Feature Request: Ability to Assign Fixed Ports for Applications in Teleport Connect #49397
Labels
feature-request
Used for new features in Teleport, improvements to current should be #enhancements
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:
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:
devnet14-1600-rpc-call should always use Port 1600 locally, even if I log out and log back in to Teleport Connect.
Similarly, other applications should use their designated static ports (e.g., 1601 for devnet14-1601-rpc-call, etc.).
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.
The text was updated successfully, but these errors were encountered: