jimradford / superputty

The SuperPuTTY Window Manager for putty sessions
https://www.facebook.com/superputty
MIT License
1.9k stars 320 forks source link

Sharing Sessions through database or shared file #909

Open skadoic1 opened 1 year ago

skadoic1 commented 1 year ago

It would be nice if the saved sessions could be shared through a somekind of database in my firm there are 3 collegues there are maintianing the network (including myself). the problem is, if someone from us is going on vacation and after he is comming back, he need to enter all changes that are made. Also, if we just copy/paste the file or reimport, the order how it ordered is from the collegue and not form the person who is importing. so i have the same session/connections but different order/sort.

And somekind of scripting/macro recorder would be nice with the abbillity to edit the macros. To automate some commands.

And a central point to add username and Passwort for connection. ex. in a database are all connections but without usernames and password. if i connect to a session it should first look at a option where i entered the credentials. if there are any, he should connect, if not, prompt for username and password

aldowski commented 8 months ago

Hello, yes, as I searched related to that option, I found this topic here. As it is already marked as New Feature Request; I would add some details.

As mentioned, in the Team's environment, members of the Team covering multiple customers and more devices per customer, do need one single shared sessions.xml file. Yes, there is a possibility to create .xml from existing .xls or .csv files; but "live connection" would be really great improvement. Example: existing CMDB database at ServiceNOW, having details about customers and devices (ip's and hostnames); that can be numbered in thousands. Cleaning unnecessary columns, removing rows with no IP may be done using some script, of course it can be done manually as well. But, it has to be done periodically, one time per week, or sometimes more often and that sessions.xml file has to be copied to all members of the team, local Superputty folder. There is a possibility to create shared folder with the file, accessible by all, and that file may be used simultaneously by all members of the Team (that may not be bad as well, I may do that, hopefully with no issues, the only possible issue is how to "say" to Superputty that folder of the sessions.xml file is somewhere else and to avoid possible delays during reading of the file by more users). Related to the suggestion for new feature here: if there is a proper link to backend CMDB database and if it is easily accessible to all users with proper credentials, some script may prepare connection from Superputty to the database, using those columns which are being used from the sessions.xml, excluding other ones. Next steps may be more complex, related to the access to the different customers using different jumphosts (which are to be prepared, set at the Putty settings), and based on the customers name, proper Putty profile may be used when being accessed. Some of possibilities may be solved using Powershell, some not.

Again, this request for new feature is great.