Article View: bit.listserv.l-vmctr
Article #720Re: VMSECURE and 'logonby'
From: Bill Williams
Date: Thu, 14 May 1992 04:54
Date: Thu, 14 May 1992 04:54
45 lines
2911 bytes
2911 bytes
On Wed, 13 May 1992 09:02:12 BST Graham Bryan said:
>We have a few instances where a VM username is accessed by a number
>of people using the 'BY/<username>/<password>' facility within
>VMSECURE.
>
>One of the people controlling one of these 'shared' usernames has
>asked if if it is possible in some way to 'get-at' the username
>used as part of the 'BY' password. The idea would be that this
>would then be used to configure part of the enviroment for the
>shared username (e.g. adding the correct signature to any
>electronic mail set out).
>
>Does anyone know if this sort of thing is possible, or have and
>suggestions one how something similar might be doen?
Just a thought or two....
Be sure that the VMSecure RULES for the target user which ACCEPT LOGONBY
has the 'HISTORY' option, and that you have generated some (say, 10-20)
History records (GENHS command). Once logged in the "VMSECURE HISTORY"
command will display however many history records you GENHS'ed; you can
use this in a Rexx/EXEC with something such as WAKEUP or IUCVTRAP to
fetch the ID from the BY/.... and do what you will with it. (I would
put it into a GLOBALV SESSION variable.) If you use this method
be sure to set the VMSecure option to immediately update the userid
rather than 'batch' updates every so often, otherwise the HISTORY won't
show up for a minute or two and you will probably want to capture it
right away -- probably in the PROFILE EXEC. (In VMSecure config
file 'DELAYHIS 0' will accomplish this. The default is DELAYHIS 60.)
Another method would be to use one of the VMSecure exit's to make the
BY/userid information availble to the LOGONBY userid. POSTRULE exit
probably? In this case you can handle how you want to do it in any
number of ways.
My remarks are based on: VMSECURE 4.2D
newer release may have more capability in exits and/or the ability
to stack all queries -- such as VMSECURE HISTORY.
---------------------------------------
Bill Williams -- ETSU Systems Support
East
Tennessee (615) 929-6853
State
University <CMS2@ETSU.BITNET>
Technical Details
Message-ID:
<L-VMCTR%92051401142891@VM1.CC.UAKRON.EDU>Path:
arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!ETSU.BITNET!CMS2Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fe320,18d5b055bc83804b
X-Google-Attributes: gidfe320,public
X-Google-ArrivalTime: 1992-05-13 19:18:16 PST
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Path: arc1-ca.pugleaf.net!sparky!uunet!paladin.american.edu!auvm!ETSU.BITNET!CMS2
Organization: East Tennessee State University
Message-ID: <L-VMCTR%92051401142891@VM1.CC.UAKRON.EDU>
Newsgroups: bit.listserv.l-vmctr
Date: Thu, 14 May 1992 00:54:59 EDT
Sender: VMCENTER Components Discussion List <L-VMCTR@AKRONVM.BITNET>
From: Bill Williams <CMS2@ETSU.BITNET>
Subject: Re: VMSECURE and 'logonby'
In-Reply-To: Message of Wed,
13 May 1992 09:02:12 BST from <J.G.Bryan@BHAM.AC.UK>
Lines: 45