Yes, really.
I've never seen this on Portal.
When users log out of Portal, they are presented with a screen saying, "You have been logged out" . Yes obviously they have!!
There is NO log in and password field which user can enter the id and password.
This happens for all users and it doesn't matter which portal role xml they are using.
This is Windows with Env 9.0.1.4 , Apps 9.0.1.2 and Portal version 9.0.1.4.199
Thanks in advance,
Roger
It seems that I am a minority here. I like this feature and to me its an added security. We are not there yet but I wish Lawson also adds a button to close the window after a logout. We have common computers and closing the instance of IE is the surest bet the that employee cache is released.
IMHO
Actually, this did not occur in 9.0.1 until 9.0.1.4. We were on 9.0.1.2 for quite a while and did not have this issue until we upgraded. We're running on the HP Integrity server HP-UX 11.23. And like most of the people on here, our users did not like this so called "enhancement". Has anyone started the enhancement request that we can all put the "me too" on? If not, I'd be glad to start one.
Jeff
I suspect that Lawson implemented this as a workaround for a security issue that as far as I know has not been resolved. In some cases, when a portal user signs off, and signs back on using the same browser and using a different userid, some (but not all) security checks may be performed using the prior userid rather than the new userid. I have observed this with MSCM using DSSO and have been told by Lawson support that it can affect other applications including LBI, and that no fix was available.
This appears to be due to some kind of caching. For this reason and others I have advised users to ignore the log out option and just close the browser window since this prevented the occurance of two known issues.
If you were to enter a new URL to re-login using the same browser or otherwise defeat this change you may encounter the above security problem, at least if the new login is for a different userid. I have not seen any issues when logging back in using the same usierid.