You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-dev@portals.apache.org by "Ate Douma (JIRA)" <je...@portals.apache.org> on 2005/10/31 23:49:55 UTC
[jira] Closed: (JS2-312) Security Credential Login Information Cached, Can't reset Admin user with restarting server
[ http://issues.apache.org/jira/browse/JS2-312?page=all ]
Ate Douma closed JS2-312:
-------------------------
Resolution: Fixed
The default "out-of-the-box" security configuration no longer disables an account.
So, this no longer is much of an issue.
Credential caching is still happening but generally I think that "is a good thing" performance wise.
> Security Credential Login Information Cached, Can't reset Admin user with restarting server
> -------------------------------------------------------------------------------------------
>
> Key: JS2-312
> URL: http://issues.apache.org/jira/browse/JS2-312
> Project: Jetspeed 2
> Type: Bug
> Components: Security
> Versions: 2.0-M4
> Reporter: David Sean Taylor
> Fix For: 2.0-FINAL
>
> The max password failure is set at 3. I think this should be higher for the default portal out of thebox.
> I used up my 3 on the admin account. Couldn't login as admin.
> So I went over to MySQL, reset the database fields, and still , could not login
> Shutdown my browser, restarted a new browser.
> Still same error.
> Had to recycle Tomcat to clear the internal cache on the User Credential state.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-dev-unsubscribe@portals.apache.org
For additional commands, e-mail: jetspeed-dev-help@portals.apache.org