Prev
Next
Forums Infor / Lawson Platforms S3 Security

LOGAN security

 3 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
prithwee
Basic Member
Posts: 20
Basic Member
4/11/2006 3:51 PM
    I am not sure about LOGAN security. Do we need to give users LOGAN at all? Some of our users are approvers in processflow so I know that that they need to be given security to WF23 atleast so that they can write comments. (atleast their comments end up in WF23). Some are EDI users. But for most crowd, what is the minimum access?

    Please let me know.
    Alex Tsekhansky
    Veteran Member
    Posts: 92
    Veteran Member
    4/12/2006 2:45 PM
      Hello, Prithwee!

      If your users use Portal, or ANY of the web applications (even web inbasket rather than Portal Inbasket), some LOGAN access is needed. RD30 is always consulted to determine your parameters during login. Other forms and tables are used as well depending on the applications.
      prithwee
      Basic Member
      Posts: 20
      Basic Member
      4/12/2006 3:12 PM
        Our users are all portal users. And many of them will use portal inbasket. ( No we b inbasket). At present, we have BC, BS, ED, EP, LA, LO, RD, SC and WF systems under LOGAN. I feel ( just a feeling based on looking at the forms! ) that I can safely take BC and SC out. Not sure about how much access should be given for LO, WF, RD. EP and LA do not have any forms, just some files. CKPOINT is a part of LA. Can anyone help?
        Alex Tsekhansky
        Veteran Member
        Posts: 92
        Veteran Member
        4/12/2006 10:23 PM
          CKPOINT is used for batch jobs. If those users do not run them at all, probably you do not need LA. Form and file access depends not only on the "general" applications, but what exactly those applications do (e.g. Portal Inbasket, while using WF, might use other codes depending on the task, possible customizations etc).
          The only way I know to determine the exact list is to:
          1. turn on DME, AGS and IDA logging
          2. Do ALL POSSIBLE combinations of tasks that might touch LOGAN
          3. From web server log extract information about calls to forms (AGS), tables (DME) and drill-around (IDA). Note that some applications (e.g. Requisitions XML) may use a different path to data, via special Lawson-delivered servlets; and some CGI programs may access data as well