Conference azur::mcc

2269.0. "MCC_TASKMAKER.COM and MCC_PROXYMAKER.COM" by TOOK::DMCLURE (Just Say Notification Services) Tue Feb 04 1992 14:45

    	I would like to offer up two potentially useful [VMS only for now]
    command procedures for setting up proxy accounts via the TASK object.
    Since we tend to rely on the TASK network object for certain DECmcc MM
    operations, I thought it might be useful to provide users with an easy
    way of creating a password protected TASK object for use by DECmcc
    management modules.  Password protected TASK 0 network objects are
    necessary in order to pass muster with DECinspect (which currently
    complains about unprotected TASK 0 objects due to their propensity
    to attract network viruses).

    	The two procedures (MCC_TASKMAKER.COM and MCC_PROXYMAKER.COM)
    can be copied from the following directory:

    		TOOK::USER$216:[DMCLURE.PUBLIC]MCC_*MAKER.COM

    	These procedures work by first creating a TASK network object and
    an associated "DECMCC" captive account on each system requiring proxy
    access for a given DECmcc Director.  This is done using the procedure
    called MCC_TASKMAKER.COM.  Once these two things are set up, then a
    number of proxy accounts can be created using the MCC_PROXYMAKER.COM
    procedure to provide remote DECmcc Directors to gain access to these
    systems without the need for specifying usernames and passwords for
    each operation.

    	Please note that these command procedures are not currently included
    in any MCC kit, nor are there any immediate plans to include them in any
    future MCC kits.  The code is farily stable (I stole most of it straight
    from the DECpulse Network Asset kit), but so far it has only been tested
    on a VAX 2000.  I'd be interested to hear whether these procedures are
    useful to anyone (as well as if there are any problems with them, etc.).

    				    -davo

p.s.	Comments displyed at runtime for the two procedures follow the FF...


MCC_TASKMAKER.COM

    	This is an optional procedure which is run from a priviledged
    account on a VMS node which is to be managed by DECmcc.  The procedure
    establishes a password protected TASK network object and associated
    captive DECMCC account.  The existence of the password protected TASK
    object and associated captive DECMCC account allow specified DECMCC
    Director users on remote nodes to be set up with network proxy accounts
    using the associated MCC_PROXYMAKER.COM procedure.


MCC_PROXYMAKER.COM

    	This is an optional procedure which is run from a priviledged
    account on a VMS node which is to be managed by DECmcc.  This procedure
    creates a network proxy account for an existing captive DECMCC account
    (which must first be created using the associated MCC_TASKMAKER.COM
    procedure).  The resulting DECMCC proxy account allows a specified
    DECmcc Director user to access a given VMS system for various DECmcc
    management purposes (without needing to specify username and password
    information for commands which would normally require such access).