Or better yet, let the user login with their existing google, fb, etc accounts so you don't have to store any pw at all! That's one of the benefits of doing this for sites/games. You don't want to be responsible for user PW's. If your server/db gets hacked you could be screwed and on the hook legally if they find your practices not up to par.
If your game isn't that big of a deal or relaxed or it's not the end of the world if something gets lost or mixed up then skipping any username/pw could be an option. For my game that stores a couple stats that isn't a big deal I'm not making the user make a username/pw. Instead I'm just making a GUID for each profile, storing it locally on their device and in the server DB. When they connect I just send it along as the ID of that device/person. Can that guid be hacked on the client side and used by someone else? Yes. Is it really the end of the world if that happens? No. Backups are made on the DB and any cases of this can be fixed, and the game isn't that serious in the first place. Just something to think about.
Edited by rpiller, 27 November 2013 - 05:56 AM.