|
|
|
Forum Newbie
Group: Forum Members
Last Login: 3/12/2007 9:26:12 AM
Posts: 6,
Visits: 6
|
|
| If you are using a share location, how do you implement usernames and passwords for auto login capabilities? Due to auditing requirements we cannot create "Admin Accounts" (so that username and password would be the same used by all users of the shared xml files). I think there may be a feature upgrade request so that there could be a centrally managed list of servers S-Code files and have the ability of the users "pulling" the list of servers be able to feed in their current username and password into the user name and passwords list for each server. To be more clear: Have a way of segregating the list of server, hostnames and folder organization settings so that you could pull the list of servers from a network share but then be able to use a "local file for the passwords and user name globally either via a local app stored setting or be able to just poll and pull the current username and password of the workstation session into a cache and to use in logging into servers (the username and password are synchronized across about 35 domains in our company so the username and password would need to be pulled separate from the domain in order to work in our scenario. I can think of a way to keep the server ip, hostname and folder organization pulling from a network share location and by writing a script to poll the information from the workstation user session and insert into the corresponding XML fields to work but I am hoping to get S-Code to make this feature available somehow so that large "Enterprise" users could centrally manage the list of servers, IP's and folder but be able to "pull" in security specific information such as username and password. Put another way we would need a way to Centrally manage the server IP information so it could be used by 100 engineers who all work on the same servers and IP but have different user names and passwords while having the ability to use the AutoLogin feature that providing the username and password provide. Right now we can centrally manage the server IP and folder organization by using a dummy userame - but we then have to type our user and password for every login to a RDP session (we sometimes open 20 servers at a time.)
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Yesterday @ 6:45:42 PM
Posts: 871,
Visits: 1,428
|
|
Thanks for the excellent post. There some good news I want to share with you.
The logon credentials templates are stored in a separate file. The file is located in the folder set via Tools->Options->Advanced->Configuration path. And as you can notice there is a separate path for registered computers list. So basically the feature you are looking for is already available in the current version. But you should keep in mind the following issue. If you set "Configuration path" to a non-shared location, this means that the VNC Manager's settings won't be shared as well. Which is actually could be a good thing.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|
|
Forum Newbie
Group: Forum Members
Last Login: 3/12/2007 9:26:12 AM
Posts: 6,
Visits: 6
|
|
| That is my point. Being able to store login credential locally to workstation but the server configs in a share location would be advantageous to my company\team and to others I would imagine as well. jamey
|
|
|
|
|
Supreme Being
Group: Administrators
Last Login: Yesterday @ 6:45:42 PM
Posts: 871,
Visits: 1,428
|
|
Jamey,
when I wrote "VNC Manager's settings " I didn't mean the registered computers list, but just the settings that can be set via Tools->Options. So to clarify my statement - the feature you are loooking for is available in the current v3.6.
Kindest Regards,
SmartCode Solutions Support
|
|
|
|