| Issue 243: | User logins | |
| 1 person starred this issue and may be notified of changes. | Back to list |
Sign in to add a comment
|
We will need user logins for things like user defined catalogues. However, a more pressing need is to have an Admin user for an install of Simal. The admin should be the only person who gains access to the ToolsPage and SettingsPage since harm can be done to the installation from those pages. |
||||||||||||||||
,
Nov 21, 2009
(No comment was entered for this change.)
Status: Started
Owner: rgard...@apache.org |
|||||||||||||||||
,
Nov 21, 2009
Implemented basic login functionality in: uk.ac.osswatch.simal.wicket.LoginPage uk.ac.osswatch.simal.wicket.SimalAuthorizationStrategy At present only the ToolsPage is protected and there are no real login accounts, just use "simal" for both username and password. This implementation is deeply flawed right now, for example the authentication status is in a static variable in LoginPage, making it useless in a multiuser environment. But it's a start. |
|||||||||||||||||
,
Nov 22, 2009
Moved classes to their own authentication package. Created a SimalSession object that stores user data so this is now usable. We still don't back the system with real a user database though, so it still isn't totally usable. |
|||||||||||||||||
,
Nov 23, 2009
Default admin username and password can now be set in local.simal.properties (set simal.web.admin.username and simal.web.admin.password). Lowering priority and moving to a later milestone.
Labels: -Priority-Critical -Milestone-0.2 Priority-Low Milestone-0.3
|
|||||||||||||||||
,
Today (14 hours ago)
(No comment was entered for this change.)
Status: Accepted
|
|||||||||||||||||
| ► Sign in to add a comment | |||||||||||||||||
