• Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint

Login Screens

Similar to the registration process, logging into the system also takes two screens—one to collect and check the user information, another to display a bad login message. As we did yesterday, we'll be setting a session variable to track the user after he's logged in. We won't, however, be setting that variable by hand! The UltraDev authentication system will internally set a session variable containing the current user's username—we can use that variable rather than editing the code!

Note

The UltraDev user authentication behaviors store the username of a person with a valid login in a session variable. Storing the UserID would be a better choice because it would open up the possibility of allowing a user to change his login name at a later time (primary keys cannot change!). Because we're working with the assumption that all usernames are unique, there's no problem.



PREVIEW

                                                                          

Not a subscriber?

Start A Free Trial


  
  • Creative Edge
  • Create BookmarkCreate Bookmark
  • Create Note or TagCreate Note or Tag
  • PrintPrint