Prev
Next
Forums Infor / Lawson Platforms S3 Security

lawsec is giving Security Violation to Lawson user on Windows 10.0.9

 4 Replies
 1 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
Russell E
Basic Member
Posts: 16
Basic Member
9/30/2019 9:17 PM

    Does anyone know how to get the lawsec utility on Windows 10 to not give a security violation.  I am running it from the command line.  I also am not able to submit a batch job from the LID.  It does submit from Portal.   I do not see lawsec anywhere in the lawson security adminiatrator.  This is one of my test environments, while in my other enviroments I am not having any issue running lawsec,

     

    I am running LSF 10.0.9



    JimY
    Veteran Member
    Posts: 510
    Veteran Member
    10/1/2019 9:28 AM
      I get the error also, but I don't generally run the lawsec command. What are you trying to do and what error do you get when you try to submit a batch job?
      Russell E
      Basic Member
      Posts: 16
      Basic Member
      10/1/2019 9:24 PM
        I am getting a security violation in both cases.
        JimY
        Veteran Member
        Posts: 510
        Veteran Member
        10/2/2019 9:40 AM
          For the issue with submitting jobs we have that problem when the user is not set up on the LSF server in a group that is setup for lsf users. Go to your LSF server and check to see which group that the lawson user is in (or other users that can submit jobs from LID) and try adding your user id and see if that resolves your issue with that. For the lawsec issue not sure what I can suggest as I don't know what you are trying to do. Good luck.
          Alex Tsekhansky
          Veteran Member
          Posts: 92
          Veteran Member
          10/3/2019 3:12 PM
            There are several requirements for the "lawsec" to work:
            1. The user that runs it must be a member of a Windows group defined in laconfig
            2. The user must have certain security roles in LSF
            3. You may need to have access to certain environment tokens in LS security

            Re: batch job - this may or may not be a separate issue, since on Windows the BATCH jobs are often configured to run via a separate special privileged identity.