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

Conference iosg::all-in-1_v30

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

277.0. "Management Authentication - not always viable" by TRNING::ALLERTON (Yesterday's solutions...Tomorrow) Thu Mar 19 1992 13:23

    
    ALL-IN-1 Version 3 introduces a new mechanism for Management
    authentication (OA$MANAGER identifier and an initialization script),
    which allows MANAGER and ADMIN form library references to be removed
    from the profile.  More space is therefore available for other FLB
    references, and there is less overhead associated with process 
    initialization.
    
    However, certain Management operations still require the MANAGER
    and ADMIN FLB references to be recorded in the profile - e.g. an
    account that is to be nominated as an Application Manager must have
    them, as do designated accounts specified in SM_POLICIES.  I find
    this a little disappointing....why introduce the new and elegant
    authentication mechanism, while still forcing the use of the
    traditional requirement?
    
    Thanks,
    
    Steve
T.RTitleUserPersonal
Name
DateLines
277.1maybe another timeIOSG::TYLDESLEYThu Mar 19 1992 15:0715
    Steve,
    
    OA$MANAGER was indeed added as a means of authentication other than
    simply the presence of the MANAGER library in the Profile. But the 
    accounts to which you refer, Manager itself, and the BATCH_ACCNT 
    account in Policies are used to run many, many batch jobs, from 
    User Management to Housekeeping. When they run, they assume that 
    form libraries MANAGER and ADMIN are open. For this reason, they 
    need to have the form libs in the Profile field. I remember we
    considered at one stage going through all the relevant coms and 
    scripts adding explicit oa$flo_opens, but the task was too great 
    and risky at the time, and we didn't have the resource.
    Sorry.
    
    DaveT                                                  
277.2The reasoning I heard...IOSG::TALLETTMit Schuh bish hiFri Mar 20 1992 08:238
    
    	and I heard the reason for doing this was so that you could have
    	more than one MANAGER, and only the MANAGER that actually runs
    	the batch jobs needs the formlibs in his PROFIL. It does, however
    	seem to be causing some confusion.
    
    Regards,
    Paul
277.3Was confused/am appreciativeGLOVES::ALLERTONSteve Allerton 343-0205Fri Mar 20 1992 22:399
    
    Dave/Paul,
    
    Thanks for responding.  Perhaps "disappointing" was a poor choice of 
    words.  "Confusing" would have done the trick.
    
    Regards,
    
    Steve