Minimum security settings

I am on Lawson Portal 9.0

My guess for 8.0, is you set CheckLS = No on RMID for the user. This will direct security settings based on LAUA.

Hope this helps.

Paul, are you referring to which LOGAN app / env tokens a user would need to have in their security class?

For some reason, when I ran secdump / secload to move security settings to a new environment as part of our LSF migration, secload automatically gave security classes access to some logan tables that they did not have previously have.

At any rate, it has been my observation that accessing portal with LSF and 803 applications required at least the following tables: LOBKMARK, LOGRPBKMRK, LOPERSBKMK, LOUSRBKMRK, & LOUSRBKOPT. There may be others too, but these are the ones I had to add to certain users. I also added the VERSION table, not sure if that was required.

If I remember correctly not all these tables existed in the 8.0.3 environment however.

Yes. The essential LOGAN items that must be included in their security class in order to access the Portal; and likewise the essential environment tokens that must be included in their security class in order for them to be able to function.

I would just give them access to all tables in LO, LA system codes (sure, you can call me lazy...) since that just gives them access to the tables themselves, not the ability to update them. Then, they also need access to the RD30 form in order change their user preferences.

I don't know about the rest of you, but I've always considered it a HUGE security risk (well, maybe not HUGE, but Large) that user preferences requires RD30, since that opens up the world to a savvy-enough user. In other words, if think your Lawson system is secure, give me an ESS or Portal account, and I'll show you otherwise...