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?
check the domain controller user account's name if it's uppercase? LAUA pulls the account name straight from DC.
>>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?
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.