How many times a day do you log in to one host or another? How many host account names and passwords do you use? If you are like many system administrators, developers, or testers, your answers are something like, “I log in to lots of host systems, lots of times during the day.” and, “I use the same account names and passwords over and over during the day.”.
Wouldn’t it be nice if something existed for all connection types that could prevent so many repetitive logins during the day? Whether you are logging in to NonStop systems, or Unix, or IBM hosts, wouldn’t it be great if something could reduce the number of times each day that you have to provide a host system with your account name and password from many times to just one time?
OutsideView has that ability. At no additional charge, OutsideView’s Identity Management capability allows you tag each session file, for which you want to use the same credentials, with the same “ID Type”. When you open the first session with a given ID type, you will be prompted for your credentials. Those credentials will then be cached, encrypted, in memory only (never in a disk file), for as long as OutsideView remains active. Thereafter, each time you open or reopen sessions with that ID Type, OutsideView will log you in automatically. Do you open seven copies of the same session file? You would only have to provide your credentials once, to watch all seven sessions logged in automatically. Do you open various sessions to various hosts, all using the same credentials? You would only provide your credentials once. What if you have a workspace that opens 15 sessions, connecting to four different hosts, and three different user names (e.g. ID Types)? You would input the three usernames and passwords once, then you can watch as all 15 sessions open and login automatically. Since credentials are cached for as long as OutsideView remains active, you could even close that workspace, open another, and watch all sessions (with matching ID types) in that next workspace login automatically too. You would be prompted for credentials only when opening a session with a newly encountered ID type.
Think about it… How many keystrokes, how much time, would you save each day If, for each user account name and password combination, you only had to enter it once?
Finally, if that is not benefit enough, an extension of Identity Management called Session Cloning, lets you activate an identical copy of an active session file, complete with automatic login, simply by right-clicking on an open, ID-managed session in the session bar.
Example 1: A workspace containing 6 sessions has been activated. Some sessions are tagged with the ID Type “NonStop User”, other are labeled with the ID Type “Super”. OutsideView prompts for the credentials to associate with each ID Type once, and will then log in all 6 sessions automatically.
Example 2: A subsequent workspace, this one containing 12 sessions, has been activated. Some sessions are ID Type “NonStop User”, others are ID Type “Super, others are ID Type “Unix/Linux User””. Since OutsideView has already cached the credentials for “NonStop User”, and “Super”, it prompts only for the Unix/Linux credentials before logging in all 12 sessions automatically.
Example 3: By right-clicking on an open, ID-managed session in the session bar, users may start a second copy of the session, complete with automatic login (as illustrated below).
Example 4: Showing the ‘cloned’ or second session file opened and logged in automatically through a simple right-click request..
Would you like additional information about using the Identity Management and Session Cloning features in OutsideView?