History | View | Annotate | Download (12.2 kB)
Implement the ManyToOne relationship for UserLogin and User that is related to Issue 64.
Initial commit related to Issue 64. Last login should point to the user's last login.
Forbid logins from disabled users.
Stop fetching and checking the user affiliation, since we are not going to use it for determining its userclass.
Complete quota upgrades with coupons. Also fix equals() and hashCode() for Invitations to consider the name or its components.
- Initial implementation of quota coupon workflow. Userclass modifications are not happening yet.- Factor out the common servlet methods into a base class.- Style the error messages in registration and coupons.
Redirect to login for browser requests without a cookie present and also for requests with cookies but without the proper one.
Now that we keep around the cookie, give the user the opportunity to use it as the authentication token to get to a file. This way passing around simple file resource URIs is possible, and as long as the user has authenticated with the service in the current browser session, he can access the file. Furthermore, treat such simple browser access as a special case and redirect to login before returning back to the file. Now one can e-mail the file URI to another user and he can click on the link, get prompted to login (or even register for the service) and then get back to the file URI to download it automatically....
Split persistentId into identityProvider and identityProviderId for easier DB queries.
Store the time the user last logged-in. Since the user object is now modified in every login, drop the updated flag optimization. Also, remove an obsolete EJB method.
Retrieve the persistent-id from Shibboleth and store it in the DBMS for future use. Also, fix a few warnings.
Log any persistent-id attributes from Shibboleth.
Don't waste time constructing the cookie for the iPhone client login case.
Allow login in development mode to utilize the GWT 2.0 browser plugin.
Avoid a NPE when the next parameter is empty.
Parse the nextUrl parameter with URI instead of URL so that chrome: URIs can be used for redirection. This should simplify the login process for Firefox extensions.
Use a different strategy for login in development environments that does not require me to recompile the web client for production deployment. Now, if the testUsername property is found in gss.properties the server treats the value as an authenticated username....
If no WebDAV password has ever been generated, copy token to it at initial login, to make sure user sees value in Show Credentials dialog.
Add system-generated password for WebDAV. (Bug #705)
Remove the redundant gss top-level directory.