WLS security realm settings cause user lockout and that's a problem (was Changing passwords locks ou
(note this topic has been edited to account for new information - BKD)
Environment
Agile PLM Version: 9.3.0.1 build 19
Update Versions: 9.3.0.1;9.3.0.1.21;9.3.0.1.38;9.3.0.1.34;9.3.0.1.30;9.3.0.1.68
WLS 10.3
Problem
Our Service Desk and end users have a long-standing complaint: a changed a password for an Agile user sometimes or always takes 10-20 minutes to take affect. This affects the web client - java client users are able to login as soon as the change is committed.
Finally duplicated this in our PY (prototype) environment, today.
What's happening is the user is locking their account
####<Mar 20, 2012 11:09:04 AM CDT> <Notice> <Security> <co-ap-945> <co-ap-945> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332259744028> <BEA-090078> <User gb39 in security realm AgileRealm has had 5 invalid login attempts, locking account for 30 minutes.>
Environment
Agile PLM Version: 9.3.0.1 build 19
Update Versions: 9.3.0.1;9.3.0.1.21;9.3.0.1.38;9.3.0.1.34;9.3.0.1.30;9.3.0.1.68
WLS 10.3
Problem
Our Service Desk and end users have a long-standing complaint: a changed a password for an Agile user sometimes or always takes 10-20 minutes to take affect. This affects the web client - java client users are able to login as soon as the change is committed.
Finally duplicated this in our PY (prototype) environment, today.
What's happening is the user is locking their account
####<Mar 20, 2012 11:09:04 AM CDT> <Notice> <Security> <co-ap-945> <co-ap-945> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1332259744028> <BEA-090078> <User gb39 in security realm AgileRealm has had 5 invalid login attempts, locking account for 30 minutes.>
0