Can you please add support for environment variables (like those supported for ext applications) in the fields in connection properties? It makes for much more flexible connection object creation.
We need this to work (this is easy for you to implement) – then we can copy connection objects and just rename them, and this parameter cascades down:
![[Image: cVQMBgp.jpg]]()
As an added “more flexible” solution that would support ad-hoc connections, also support something like this:
![[Image: mjovfQg.jpg]]()
The (/prompt "Servername") would prompt the user with "Servername:" and would substitute the response in place of the parentheses section.
This would allow specification of a name when they connect – allowing multiple prompts would provide best flexibility.
While I’m shooting for the stars with requests, we have an issue of these connections pointing to a statically numbered “dynamic” proxy account. If two people specify the same number on their connection, and attach to the same machine, the accounts will collide and the second one will be denied. Support for the concept of a randomized number generated at connect time would reduce likelihood, as well as improving chances that a retry would use an unused account:
Proxyacct-DomA(Random(01-29))@mydomain.loc would translate to proxyacct-DomA15@mydomain.loc on an example connection request. The smartest nomenclature for specifying this “random” token may not be as I’ve shown, you likely have better ideas.
![[Image: 5uZBFbY.png]]()
We can work with option 1; option 2 allows ad-hoc, option 3 is pie in the sky and just reduces potential for account collision.
Will you please consider this?
We need this to work (this is easy for you to implement) – then we can copy connection objects and just rename them, and this parameter cascades down:
![[Image: cVQMBgp.jpg]](http://i.imgur.com/cVQMBgp.jpg)
As an added “more flexible” solution that would support ad-hoc connections, also support something like this:
![[Image: mjovfQg.jpg]](http://i.imgur.com/mjovfQg.jpg)
The (/prompt "Servername") would prompt the user with "Servername:" and would substitute the response in place of the parentheses section.
This would allow specification of a name when they connect – allowing multiple prompts would provide best flexibility.
While I’m shooting for the stars with requests, we have an issue of these connections pointing to a statically numbered “dynamic” proxy account. If two people specify the same number on their connection, and attach to the same machine, the accounts will collide and the second one will be denied. Support for the concept of a randomized number generated at connect time would reduce likelihood, as well as improving chances that a retry would use an unused account:
Proxyacct-DomA(Random(01-29))@mydomain.loc would translate to proxyacct-DomA15@mydomain.loc on an example connection request. The smartest nomenclature for specifying this “random” token may not be as I’ve shown, you likely have better ideas.
![[Image: 5uZBFbY.png]](http://i.imgur.com/5uZBFbY.png)
We can work with option 1; option 2 allows ad-hoc, option 3 is pie in the sky and just reduces potential for account collision.
Will you please consider this?
. Just moved from one company to another a few months ago and convinced my team to use the product. 