Prev
Next
Forums S3 Systems Administration

Loadusers

Sort:
You are not authorized to post a reply.
Author
Messages
pops
Advanced Member
Posts: 46
Advanced Member
5/15/2015 5:55 PM
    When using Lawson Interface Desktop and then LAUA and looking at the users displayed, there is one user appearing that was deleted using the Lawson Security Administrator.  When deleting the user via the Security Administrator and then going starting LID and then LAUA the user is normally gone.  This one somehow is still there but with no information within the users profile.  I checked for orphan profiles but there are none.  If I create the user again using the Security Administrator and then use LID and then LAUA the user appears twice.  If I go into one of the profiles and set up the User group,etc.  when the user goes into the Lawson Portal and tries to run a GL290, GL190, etc.  after entering all the required fields, when they submit the report they get the message something like "required field" but it doesn't tell you which field and everything that is required IS filled in.  The problem is because there are two profiles.  I cannot seem to delete the one that is "stuck".  I wanted to try loadusers but I have no idea what the name of the xml file is names in order to try to delete the user that way.  Can anybody help me?  The user cannot do anything until this is fixed.  The current status is that I deleted the user using the Security Administrator which only removed one profile in LID/LAUA.  We were thinking of deleting the user's AD account but it's tied to other applications that would have to be reconfigured and is not an option.  Thank you in advance!
    Brian Allen
    Veteran Member
    Posts: 104
    Veteran Member
    5/15/2015 6:04 PM
      I've seen similar issues before that were due to orphaned records in LDAP. Try using Jxplorer or an LDAP browser and check under lwsn, lwsnSecData, svcXref.
      Greg Moeller
      Veteran Member
      Posts: 1498
      Veteran Member
      5/15/2015 6:08 PM
        Why not just do an F9 when the user is selected in LAUA? Won't this get rid of the profile?
        TBonney
        Veteran Member
        Posts: 277
        Veteran Member
        5/15/2015 6:11 PM
          Is the user's domain userid tied to more than one rmid? To check, go to Manage Identities in Lawson Security, select your environment name from the list of 'Services' on the left. Then, on the right, on the select identities tab, choose domain_user in the second drop down and provide your user's domain account. Click the Add Criteria button, hit the 'Execute Query' button. Then, go to the 'Results' tab to view the results...When you highlight the sid at the top, it will display (at the bottom) all RMIDs assigned to that sid.

          If there are more than RMIDs one listed, this could be your problem. (If so, to fix, go to the Manage Identities Tab under user Maintenance for the unwanted userid. Again select your environment and validate/correct the domain user listed. If incorrect, you can correct it here and it will pull in the new SID, correcting the issue.)
          pops
          Advanced Member
          Posts: 46
          Advanced Member
          5/15/2015 6:33 PM
            No it's not tied to more than one rmid. It was suggested by another person in IT that we should delete the user's AD account. I don't know if that will fix the problem or not.
            pops
            Advanced Member
            Posts: 46
            Advanced Member
            5/15/2015 6:43 PM
              Brian:

              Can you give me more detailed instructions. I am not that familiar with Jxplorer.

              Thank you!
              Brian Allen
              Veteran Member
              Posts: 104
              Veteran Member
              5/15/2015 7:18 PM
                It's always best to have an LDAP administrator or someone familiar with LDAP if possible.
                You can use a free download of LDAP Browser or Jxplorer to connect to your LDAP with the connection information that was used to connect Lawson to it.
                Once connected, you can navigate the tree (point and click) and look under the lwsn - lwsnSecData - svcXref node and lwsn - lwsnSecData - idXref nodes. Orphan records are usually under idXref.
                Under this tree are the 4 types of identities and you search for the bad record and then delete it.

                Anytime you manually update the LDAP, it is good to get a backup in case you remove the wrong ones.
                pops
                Advanced Member
                Posts: 46
                Advanced Member
                5/18/2015 3:15 PM
                  Excuse my ignorance, but where in Lawson can I find the connection information to the ldap server?
                  Greg Moeller
                  Veteran Member
                  Posts: 1498
                  Veteran Member
                  5/18/2015 3:20 PM
                    You can find some information in $LAWDIR/system/install.cfg under the LDAPHOST and following variables.
                    pops
                    Advanced Member
                    Posts: 46
                    Advanced Member
                    5/20/2015 1:57 PM
                      Problem fixed. We ended deleteing the user from Lawson and then deleting the AD account and recreating it and then recreating the Lawson account and the duplicate record is gone. Thanks everyone for your help and suggestions.
                      You are not authorized to post a reply.