Prev
Next
Forums Infor / Lawson Platforms S3 Security

Securing Development Utilities LSF9 Security

 9 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
ALB
Veteran Member
Posts: 130
Veteran Member
10/15/2013 2:39 PM
    We are moving to Lawson 9 security.  We have run into a couple issues with utilities and menus used for development.  We are getting security violations for tmcontrol, but I do not see were it is located.  Also, we gave access to laenv and latools, but we receive the message "LAPM Does Not Support LS Users."  How do we get around this?
    Roger French
    Veteran Member
    Posts: 549
    Veteran Member
    10/16/2013 1:19 PM
      Check out the ENV (Environment) security profile. Most if not all of the tools and utilities are included there.

      Also remember that if user's security profile has that CheckLS=Y, then they cannot use LID for application program access, i.e. they cannot use LAPM. That's why you are seeing that message...That is the reason for using LS Security is so that they have to use Portal (not LID) for program access such as HR11, AP10, PO20, etc. Remember too that system admins with CheckLS=Y, yes they still can use LID to do system-related tasks.

      ALB
      Veteran Member
      Posts: 130
      Veteran Member
      10/16/2013 3:21 PM
        tmcontrol is not in there.  Can it be added to a group like development utilities?
        Roger French
        Veteran Member
        Posts: 549
        Veteran Member
        10/16/2013 3:40 PM
          Sure try it out and let us know how it goes.
          ALB
          Veteran Member
          Posts: 130
          Veteran Member
          10/17/2013 2:53 PM
            It worked, but I was not sure what other issues to expect.
            Greg Moeller
            Veteran Member
            Posts: 1498
            Veteran Member
            10/17/2013 3:59 PM
              Silly question: How did you add it? I'm trying to do the same thing here.
              Kwane McNeal
              Veteran Member
              Posts: 479
              Veteran Member
              10/17/2013 4:07 PM
                tokendef
                Kwane McNeal
                Veteran Member
                Posts: 479
                Veteran Member
                10/17/2013 4:09 PM
                  There are several utilities that have historically not been added to GEN\EXECUTABLE (aka 'tokendef') that should be for security reasons.
                  Depending on your release level, you may find that ssoconfig isn't there.

                  I'll see if I can dig out my full listing over the weekend.
                  Judy Consoli
                  Veteran Member
                  Posts: 43
                  Veteran Member
                  12/5/2013 2:11 PM
                    We are using LS 9.0.1.11 for users but not developers and I am trying to move developers in preparation for Infor 10 upgrade.

                    When using CheckLS=Yes for a developer, we can add a new pgm using pgmdef, but as soon as we leave pgmdef and then return, we get a security violation.  Is there anyway around this or do we have to grant access for each custom program we develop immediately?

                    In laua, the creator and those members of their security class automatically have access? 
                    Greg Moeller
                    Veteran Member
                    Posts: 1498
                    Veteran Member
                    12/5/2013 2:27 PM
                      LAUA security model is 180 degrees from LS. LAUA you get default access to everything and have to take things away that you don't want the users to have access to, whereas in LS you have to add things that you want the user(s) to have access to... by default they do not have access to anything.