Discussion:
cannot loggin to websphere commerce
(too old to reply)
t***@hotmail.com
2006-11-06 17:09:38 UTC
Permalink
I am unable to loggoin to websphere commerce tools ver.5.6.1. The message i get is "you have to wait 13245211 seconds before you can login again"
geo
2006-11-06 18:25:47 UTC
Permalink
The timeout being displayed is for the password policy.

This is called the "Consecutive unsuccessful login delay" for the account
policy.

http://publib.boulder.ibm.com/infocenter/wchelp/v6r0m0/topic/com.ibm.commerce.admin.doc/tasks/tseaccpol.htm
Post by t***@hotmail.com
I am unable to loggoin to websphere commerce tools ver.5.6.1. The message i
get is "you have to wait 13245211 seconds before you can login again"
Brian Lima
2006-11-06 18:37:05 UTC
Permalink
Post by t***@hotmail.com
I am unable to loggoin to websphere commerce tools ver.5.6.1. The message i get is "you have to wait 13245211 seconds before you can login again"
The timeout value is a result of too many failed logon attempts. For
security reasons, Commerce will start adding a timeout value to future
failed logon attempts. This is controlled by the account and password
policy assigned to the user. You can read up more on the policies in
the info centre:
http://publib.boulder.ibm.com/infocenter/wchelp/v5r6m1/index.jsp?topic=/com.ibm.commerce.admin.doc/concepts/cseauthenticationpolicies.htm
t***@hotmail.com
2006-11-07 04:49:23 UTC
Permalink
Thankx for the reply but i m still facing the same problem, i m running the Test Environment with only one account.The first thing i need to know is how to login to amdinistration console when my account is disabled for about 31471668 seconds.
Brian Lima
2006-11-08 22:33:21 UTC
Permalink
Post by t***@hotmail.com
Thankx for the reply but i m still facing the same problem, i m running the Test Environment with only one account.The first thing i need to know is how to login to amdinistration console when my account is disabled for about 31471668 seconds.
Were you able to use the info given in the other thread (updating
plcyacclck) to solve this issue? If so please note that you should go
back and review your account lockout policy and verify that it meets
with your security rules.

Loading...