Password Resetting part 2
Brandon and I just made a discovery! thanks in part to Gaia’s deep linking, we were able to implement one of the alternative options that I discussed in the previous post. Instead of sending the GET string to the newPasswordSet.php page, it will be sent directly to the passwordChange page in the quietus consulting application. Then it can call the appropriate php file after they input the new password, and then either authorize them and reset their password, or tell them they aren’t allowed to reset this user’s password (the encrypted password authentication doesn’t match up)
We need designs for (but can make up the design ourselves, based on the login page…) a page to input the email to which the reset password info will be sent, and a page where the user can input their new password (two fields, new password and re-type password)
This is more of a memo than anything, letting people know what’s in the works.
Password Resetting
The code has been successfully written to change a user’s password. Here’s how it works!
- step 1: User claims they have forgotten their password. They need to input some form of identification (whether it’s their username, email address, or user ID) so we know which user’s password to reset.
- step 2: The user is sent an email with a link they can go to which will automatically reset their password. This link has get parameters attached to it, so it will look something like this:
http://cias.rit.edu/~feedme/quietus/php/newPasswordSet.php?userID=&password=50ff4740002e975652481a30508db78f
The userID parameter is obviously the user’s ID, and the password parameter is the current user’s password as it has been encrypted and saved in the database, but encrypted again. - step 3: The user goes to the link, and the database matches the password in the string with the encrypted password in the database. If they match, a new password string of 8 characters composed of letters and numbers will be randomly generated. This new password will be sent to them via email, and encrypted and saved in the database. Now, they can log in with this new password.
- step 4: They can go to a “change password” page inside the quietus consulting application to change their randomly generated password to something they can more easily remember.
Steps to be accomplished: Step 1 and step 4. both these steps require their own pages in the quietus consulting application. Also, a page for Step 3 may need to be designed. This will be an html page.
Reasoning behind this method: This way, a user cannot falsely claim to be another user and request a password reset. If they do, the only action that occurs is that an email is sent to the user. If it is ignored, no change is made in the database. The user must actively click on the link in the email to get their password reset.
Other possible methods: If I can find a way, the link in the email could go directly to the “change your password” page in the quietus consulting application (thanks to gaia deep linking), and the user could change their password from there. This method would be much more complicated, and less secure.
Any thoughts / comments / clarification?
Imagine RIT
The team participated in the Imagination RIT fair this last Saturday and used this opportunity for user testing. The experience of watching users was great and the site got the laughing reactions that we were aiming for. Several things still need to be fixed in the next three weeks and we look forward to seeing the completed site. We have also added the user deaths to twitter so that Quietus has a twitter community and changed the take Away Page layout.
User Results:
- introduction complete
- Create your own account should be more noticeable
- Make kid friendly questionnaire level?
- Progress bar for questionnaire
- Have a ” do you have children?” question to add to stress level
- People don’t know how to drag sliders
- Agree to terms button and content
- Icons for sliders
- Arrow for isometric graph should pop more
- Animations complete
- Dropping death age by 10 years
- have immortal option
Lee helping this young fellow find his mortality.
Brandon comforting the dead...
More of the support team 
Comps Version 3
Another round of lovely comps to display.
Comps Version 2
Hooray math!
http://feedme.cias.rit.edu/quietus/php/graphData.php
Alrighty folks, this will be a quick post because I’ve got class in 4 minutes, but here goes.
the above link will take you to a page where you can choose the filter that gets graphed against the frequency of causes of deaths, and it will tell you how many people in the database are most likely to die from such a cause in their respective divisions. It also displays the percent of the highest number, as well as the number of cubes which would be displayed in flash.
enjoy!
(if you want to add more “ghost” data to the database, I made a script to do just that! it’s here: http://feedme.cias.rit.edu/quietus/php/recordsFill.php – if you want to add more than one record at a time [could get quite daunting...] then you can add ?n=# to the end of the url, where # is the number of records you want to create. If you create one, then refresh the graphData page, you’ll see the new numbers! Isn’t that exciting!?)
yikes! late to class!
Comps Version 1
Cyndy and Jae together created these versions, implementing everyone’s designs and ideas.
Information will hide and reappear when needed for the users and colors tone for background would changed depending which section they are on “home”, “about”, “explore”.
Updated Site Map
Starting the New Quarter
Feed Me has started out the first week of our spring quarter jumping back into the design and development with great excitment. The designers have made several versions of logos, preloader pages and navigation designs. We have collaborated into making an isometric feel for the preloader and will have a preloader and isometric graph page designed to give to the developers tomorrow.
In the team meeting today, we further discussed the wire frames, weekly goals, and resolved some potential problems with the isometric graph interactivity. The isometric graph is to be the first graph the developers are going to work on. Some solutions to the interactivity of the graph and the users not being able to see specific information because the front of the graph can overlap the cubes in the back are as follows:
- Make the cubes in the front of the graph transparent.
- Develop the graph using Flash Papervision to be able to slightly rotate the graph.
- Shift the topic being viewed to the front of the graph when selected.
Tori’s Comps
