PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 09/17/2019 1:58 PM by  Dave Amen
Mass way of removing update access from security classes
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
Todd Mitchell
Senior IT Specialist
Gordon Food Service
Veteran Member
(186 points)
Veteran Member
Posts:80


Send Message:

--
09/17/2019 12:50 PM
    We are in the process of moving to a new platform.  What are the best options for either keeping the same security classes and removing update access or creating new security classes with view only?
    Kwane McNeal
    Private
    Private
    Veteran Member
    (1323 points)
    Veteran Member
    Posts:441


    Send Message:

    --
    09/17/2019 1:28 PM
    Todd,
    If you’re referring to leaving an Infor platform, then I’d just set the database user to read only (aka select, connect, and execute stored procedures)

    If you need to run jobs, leave update access to CKPOINT and SUBCKPOINT, (and OVRPTRF if iSeries)

    Kwane
    Dave Amen
    Private
    Private
    Veteran Member
    (184 points)
    Veteran Member
    Posts:66


    Send Message:

    --
    09/17/2019 1:58 PM
    Hi Todd,
    Kwane has a great suggestion above for doing this globally.

    If you'd like to do this through Lawson Security, we (Kinsey) have a couple of options:
    - We have a tool which takes existing SecClasses or Roles and converts them to inquiry-only (all 200s reports are given full access, all on-line screens and 100s and other batch programs are given ALL_INQUIRES).
    - We can provide a set of Security Classes that give inquiry-only access (one SecClass per System Code which gives full access to all 200s programs and ALL_INQUIRES to everything else).

    Regards,
    Dave
    (303) 773-3535
    You are not authorized to post a reply.