[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

1271.0. "DECwindow Autologin?" by YUPPIE::LOFTIN (R. Lavon Loftin) Mon Aug 14 1989 17:45

    Is there a auto-login mechinism for DECwindows?
    
    What I mean by "auto-login" is that when a user first strikes a
    character at a logged out workstation the system automatically logges
    as a predefined user.  THere is no user name/password screen.
    
    Thank you
    
    Lavon Loftin

T.RTitleUserPersonal
Name
DateLines
1271.1STAR::ORGOVANVince OrgovanTue Aug 15 1989 23:065
    No there is no auto-login mechanism within DECwindows. I can see
    that such a feature would allow faster startups on a standalone
    workstation that was devoted to a single user. Are there other
    reasons that you want this feature?

1271.2Shared access to locally booted workstationsTALK::COTTAYJan 89: US tops 13K total warheadsThu Aug 17 1989 07:3423
                     <<< UD$1:[NOTES$LIBRARY]TALK.NOTE;1 >>>
                           -< What's going on here? >-
================================================================================
Note 227.3                      VTSAT1 standalone                         3 of 3
TALK::W_PIPER "bill piper 266-4393"                  18 lines  16-AUG-1989 07:35
                       -< VAXstation-as-terminal Redux >-
--------------------------------------------------------------------------------
                                   .
				   .
				   .

    Hmmmm...  Since a VAXstation is just a clever terminal, and we never
    had any problem using a VT100 in another's office, why not just turn
    these stripped-down nodes into autologin engines?  There is nothing to
    secure really, and anyone who can access WSA0: is already close enough
    to break in via OPA0:.  All the security checking is done via
    DWAPP_NOPROXY and its targets.  This eliminates the need for SYSUAF
    sharing or tracking or anything.  And you'll have a very clever
    terminal with the same security features as a VT100.
    
    -piper
    

1271.3VMSDEV::HENDERSONVMS Systems AnalysisTue Aug 29 1989 15:0818
Auto-login would be of great help in many OLTP shops.

Many times, the terminals in a particular department get a particular
top-level menu which meets the needs for, say payroll, and doesn't even
acknowledge the existence of other applications on the host.

In an environment of X-terminals, these buyers of large TP systems
(once they advance from forms technology to windows technology)
will want non-sophisticated data entry clerks (or factory floor workers)
to press a button/key and be 'in their environment'.
(it's all in the name of idiotproofing)

	Ken

(of course, on the factory floor, the X-terminal should be oil-proof,
and instead of a mouse: it should have a touch-sensitive screen)
[finger press = MB1 / shift-finger press = MB2 / alt-finger press = MB3]

1271.4Single user = many people39255::CRAIGNice computers don&#039;t go down :-)Wed Aug 30 1989 10:0013
    AUTOLOGIN would be a big help for some of our customers who develop
    applications with their own security system.  Typically, they set up
    a single VMS username, in a captive account which drops into the
    application, and the security checking is done at that level.
    
    It would also be very nice to have for tradeshows where you want
    someone roaming the aisles to be able to press CR, or click on a button
    and drop right into a demo.
    
    						Bob Craig
    						DSM Product Group
    

1271.5Other terminal-style features . . .SEWANE::MASSEYWang: &#039;Daddy, I shrunk the company.&#039;Sat Sep 02 1989 00:3225
On the subject of terminal-type features for DECwindows, I was talking to a
customer awhile back who had a neat idea for a "watchdog" or "chipmunk"
variant.  It seems his users are always walking off and leaving their
terminals logged in, which management considers a security risk, and he's
worried about the same thing happening when they start using workstations. 
He wanted to know if there was a way to write a program that would cause
the session manager to pause the user's session after a period of no mouse
or keyboard input.  I told him that I didn't think there was, but the idea's
intriguing, especially since this method isn't as drastic as its terminal
variations (no programs get killed, the workstation simply pauses the
session for the "forgetful" user).  Does anybody have any ideas on how this
might be implemented?

And while I'm on the subject, I've found myself walking off without pausing
my workstation.  Seems Im working away when I get a call, or somebody comes
by, and we talk for fifteen minutes.  At that point, I get up to go do
something else, forgetting that I haven't paused my workstation, and not
having any visual reminder because the screen saver's blacked out my
workstation screen.  It'd sure be nice to have a mechanism to specify that
the screen saver operate only when the session manager's paused.

If I think about it, I might submit these at the next DECwindows Phase 0.

Steve

1271.6FEATHR::BLUEJAYWar is hell - but THIS is rediculous!Tue Sep 05 1989 14:203
Maybe latch something in with the screen-saver? That already seems
to do the if-no-mouse-or-keyboard-input thing.