Is there a time out parameter somewhere within portal (current version 3.162) that will challenge a user for his/her ID and password after some period of inactivity? In my past Lawson life, it was always a requested feature, and not available through the application itself. It's happening here, and our systems engineer can't find anything, and our infrastructure guys insist they have no time outs anywhere, but I don't imagine it when it's happening to me! I'd just like to have an explanation when I'm asked - many thanks :nix:

That should be happening on the authentication source (MSAD, Novell, iPlanet, SunONE, etc). If there is no built in tool to handle this, you should be able to use a combination of LDAP queries and JavaScript on portals logon.htm to prompt the user to change their password at the source. Not sure if this is what youre looking for though.

hth,
matt

Thanks for the info, Matt - but its not exactly what I'm looking for I don't think :blink:
It's not a password change, it's a challenge to re-enter the ID and password after some period of time. I personally don't think it's in Lawson anywhere, but it would be nice to know WHERE it is since no one else will admit its in their domain!It would just be nice to be able to tell our users its a parameter somewhere and they just need to live with it. The perception is definitely that it's in the application and under our control and we should "fix" it.

My current client, and a few others on that "other" mailing list, have experienced occasional incidents of what we're calling "Spontaneous Re-authentication" - we all know for a fact that it's not Lawson related - since Lawson doesn't DO authentication... It only APPEARS to be Lawson because that is the only secured web application where the end users spend all their time.

It appears that either there is an interruption in network connectivity (but the web is stateless, so that doesn't really answer it) or that somehow the browser is losing it's credentials.

In our case it happens most often to users in our remote offices, but so far none of us collaborating on the problem have been able to pinpoint the cause.

g'luck!!