[Search for users]
[Overall Top Noters]
[List of all Conferences]
[Download this site]
Title: | *OLD* ALL-IN-1 (tm) Support Conference |
Notice: | Closed - See Note 4331.l to move to IOSG::ALL-IN-1 |
Moderator: | IOSG::PYE |
|
Created: | Thu Jan 30 1992 |
Last Modified: | Tue Jan 23 1996 |
Last Successful Update: | Fri Jun 06 1997 |
Number of topics: | 4343 |
Total number of notes: | 18308 |
3192.0. "Application Maintainer's ACL on MLA element. Why?" by 49393::KURTH (Peter Kurth @RLE, R�mlang (Switzerland)) Wed Aug 25 1993 17:18
HellO
ALL-IN-1 V3.0-1 (1st=German, 2nd=English)
User CUSTOMIZER is set as Appliation Maintainer (the SYSUAF-entry
ownes OA$PRVAPP and OA$MANAPP, PRVAPP is A).
When CUSTOMIZER processes a pending element (AM PME ML), the element
gets the following ACL:
Directory OASYS$DISK:[ALLIN1.SITE.SOURCES_SHARE]
OA$FORMATTER_START.COM;1 8 25-AUG-1993 17:06:14.54 OA$MANAPP
(RWED,RWED,RE,RE)
(IDENTIFIER=[LLE_MAIN,CUSTOMIZER],OPTIONS=NOPROPAGATE,ACCESS=READ+
WRITE+EXECUTE+DELETE+CONTROL)
(IDENTIFIER=OA$MANAPP,ACCESS=READ+WRITE+EXECUTE+DELETE)
Why the ACE "IDENTIFIER=[LLE_MAIN,CUSTOMIZER]"? If I do the same
using the MANAGER, only the ACE "IDENTIFIER=OA$MANAPP" is added, which
I think is correct.
Any idea? Is this the intended behaviour?
Regards, Peter
T.R | Title | User | Personal Name | Date | Lines |
---|
3192.1 | Looks ok to me | AIMTEC::WICKS_A | U.S.A 2 England 0 - I was there! | Mon Aug 30 1993 22:13 | 11 |
| Peter,
I think this is the way it should work though I defer to the dutchman
or the irishman for confirmation. remember MANAGER is a special user
and has all thos VMS privs and the OA$MANAGER identifier etc so s/he
has access to all the CM elements anyway so add the extra ACl for that
one would be superfluous.
regards,
Andrew.D.Wicks
|