LAUA - Some users are shown in UPPER CASE

Sort:
You are not authorized to post a reply.
Author
Messages
John Costa
Veteran Member
Posts: 154
Veteran Member

    We are on LSF9, version 9.0.0.6 using MS-ADAM for our LDAP. We are also using LDAPBind to validate users against our corporate domain. We are still using LAUA security. I understand the concept of creating Resource Managment records for users and then creating the necessary identities for the environment, self-service, SSOP, etc. The problem we are running into is that some users are showing up in LAUA with all upper-case user names whereas the majority of our users show up in lower-case. Why the difference?

    _________________ John - Wichita, KS
    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member

      check the domain controller user account's name if it's uppercase? LAUA pulls the account name straight from DC.

      John Costa
      Veteran Member
      Posts: 154
      Veteran Member
        Thanks Jimmy, been there, done that. Verified the user's name is in lower-case at the domain level. This is definitely a weird one. If I run 'laua -o', the user's name shows in lower-case. If I run 'laua' (without the -o switch), the user's name shows in upper-case. It's obviously something in the environment. Lawson is aware of the error and they tell me that their developers are working on a resolution but it will probably be after October until we see an envionment patch released that corrects the problem.
        _________________ John - Wichita, KS
        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member
          I think I know what you mean. My own login is always displayed in UPPERCASE when i run laua.
          CindyW
          Veteran Member
          Posts: 169
          Veteran Member

            >>We are on LSF9, version 9.0.0.6 using MS-ADAM for our LDAP. We are also using LDAPBind to validate users against our corporate domain. We are still using LAUA security.

            This describes us as well. However, 99% of our users appear in upper-case regardless of the -o parameter in LAUA. The only lower case ones are our Lawson admin accounts, and our training accounts - as these were all created by a consultant I suspect something in the process caused that. As far as LS, our domain_user values on the environment identities also are in upper-case. We made a decision (we were advised) to create these accounts in upper case this when we moved to LSF9.

            I think I remember that in 8.0.3, we did have many user names that displayed in lower case, but we must have eliminated that in our migration process. Just curious, what problems is this causing for you?

            John Costa
            Veteran Member
            Posts: 154
            Veteran Member

              The most immediate problem we've run into is that these particular users are not able to create requisitions within the RQ module as they are not recognized as valid requesters.   Due to the case sensitivity within the database, a requestor in Lawson with an ID of user1 is not recognized as being the same person within LSA with an ID of USER1.

              As a work-around, what we've had to do is delete these particular accounts out of LSA, stop LASE, and ensure they are set up in our domain as lower-case.  We then start LASE again, stop / restart WebSphere, and then set them up again in LSA, this time in lower-case.  Stopping and restarting LASE is necessary as it's the only way we can get the invalid upper-case user info removed from cache memory.

              _________________ John - Wichita, KS
              John Henley
              Senior Member
              Posts: 3348
              Senior Member
                There's an easier way. Just make their XXX_REQUESTER lowercase in RM and it will map to RQ04.
                Thanks for using the LawsonGuru.com forums!
                John
                John Costa
                Veteran Member
                Posts: 154
                Veteran Member
                  Thanks, John, but we don't use Requisitions self-service and therefore have no identities on the XXX_REQUESTER service.
                  _________________ John - Wichita, KS
                  Ben Coonfield
                  Veteran Member
                  Posts: 146
                  Veteran Member
                    You should be able to define a requester in upper case -- we have done so in the past although our normal practice is to use lower case.
                    You are not authorized to post a reply.