Changes between Version 5 and Version 6 of s2s-login-functionality

Timestamp:

03/24/10 18:22:07 (15 years ago)

Author:

mira

Comment:

--

s2s-login-functionality

@@ -68 +68 @@
 
  == Web UI ==
- This task is basically implementation of jspx files and HttpRequesHandlers for their logic. The present design of the WebUI and WebApp modules is good and should be kept and just extended to supprot new functionality.
+ This task is basically implementation of jspx files and HttpRequesHandlers for their logic. The present design of the WebUI and WebApp modules is good and should be kept and just extended to supprot new functionality. There will be added: 
  * Login page
-    * Two text fields for password and email
-    * Back button
+   * Two text fields for password and email
+   * Back button
+  There will be common method used for the login functionality. The handler for this page should extract and validate the data of the request. The it should call this method to login the user. 
+
  * Forgot password page: Sends the user mail with his password, after the 
   * Label that describes expected user behavior and what will happen after send button is clicked.
   * Text field for users mail
   * Send button
+ The handler will check if such user exists and if so send the original password back to him/her. The email will be send by a special asteasolutions.net mail. The mail, smpt and port for this will be put in constants so that in future they could be paramethers of the server configuration. 
+
  * Notification page
   * Template page that is shown for few seconds with message inside it. Announcing errors or success.
+
  * Registration page
   * Two columns with text fields for: e-mail, password, confirm password, screen name, description
@@ -83 +88 @@
   * Labels that point the mandatory fields
   * Labels to point any restrictions (image size etc.)
-  * Error messages appear on top of the page. Error types could be the following:
+  * Error messages appear on top of the page. Error message could contain the following error info:
    * Wrong mail
    * Short password (insecure)
    * Wrong password conformation
-   * Unable to upload image
+   * [OPTONAL]Unable to upload image
+ Since those fields are slightly different from the initial ideas for user information to be stored, the UserR4 keys and the RegistrationFormBean fields should be changed accordingly. The registration handler will deal with all fields validation. If all requered information is ok the user will be created in the users folder on the server. He/she will also be loged-in by the common method used by the login handler. If the information is not ok the handler provides error messages and returns a RegistrationFormBean that contains the valid information. This way the set fields of the bean are used as default falues for the registration form. 
+ 
  * Edit profile page
   * Basically same as the registration form, with few differences. First of all the mail text field is replaced with label. Second instead of "password" and "confirm password" fields we now have - "password", "new password", "confirm new password". Additional link to profile view is added.
+ The handler extracts all the given information and changes the stored data for the user that is curently loged in. There is additional password check. 
+ 
  * My profile page: Displays users info
   * Same as registration page, but instead of input controls we now have labels and image
- 
+ The handles simply colects all the information for the currently loged in user and sends as a regues parameter in the RegistrationFormBean.
 = Implementation =
 ^(Describe and link the implementation results here (from the wiki or the repository).)^