Masking UserID in LID and Reports

Sort:
You are not authorized to post a reply.
Author
Messages
Roger French
Veteran Member
Posts: 545
Veteran Member
    We've got a small group of users where their UserID includes the last 4 digits of the SSN. (Yes I know, I didn't create the UserID naming convention/policy.) That UserID is appearing on some screens and reports and it presents a security and privacy concern.

    Is there any way to mask the all or part of the UserID on screens and reports? If so is this a big change?

    Thanks in advance,

    -Roger

    Apps: 8.0.3.7
    OS: Win2003
    Env: 8.0.3.6
    John Henley
    Senior Member
    Posts: 3348
    Senior Member
      Do you mean like in GL where it stamps the username into the JE record and then it displays on GL45?
      Thanks for using the LawsonGuru.com forums!
      John
      Roger French
      Veteran Member
      Posts: 545
      Veteran Member
        Yes.... plus on reports (any report) where the userid is displayed.
        John Henley
        Senior Member
        Posts: 3348
        Senior Member
          Hmmmm...
          Of course, the best thing to do would be to change their user ids, then run some SQL scripts to change their userids in the existing data to their new userid. Then you'd be done.

          If you need to do it on an on-going basis, I think you're probably better off doing this via the database rather than trying to monkey with the application code. One idea I did have is that you could fiddle with the 'bldsh' templates which load CRT-USER-NAME, etc. but I think that would be pretty risky.

          So, if you really wanted to keep the userids, and just mask them in the database, you'd probably need to identify all of the affected tables, and add INSERT/UPDATE triggers to mask the values when the database gets updated. You'd need to run scripts as in the above solution in order to mask the existing data. You'd also need to make sure you keep copies of the triggers so that if the tables ever were re-created you could reapply them.

          Not a very good solution [it would be nice if there was a "SELECT" trigger, or Lawson data was retrieved via stored procedures].

          I'd recommend changing the userids!
          Thanks for using the LawsonGuru.com forums!
          John
          You are not authorized to post a reply.