search for: howtoauthenticate

Hi all- I am building an application that includes a login screen. During development I found that user passwords are logged by Rails in plain text -- this will not be acceptable to my users. Is there a way to obscure/encrypt incoming password parameters or not write them to the log files at all? One thought was to use Javascript, but I was not sure how secure that would be. Thanks, Josh

Hi, Maybe I ask again for something what is wasn''t able to find anything. Is there simple way how to process authorizations? My imagine is that some action for controllers are allowed only to few users. E. g. Everybody can look category list, but only registred user can edit or add. In best way, when user is signup, rails will remember his rights like: adding_category = false

Thanks to everyone who responded to my first set of questions. Not only did I get my questions answered but I improved my code and learned a couple new things. I think I prefer the mailing list over IRC... easier to follow :-) I have some more questions if you don''t mind. Some are Rails related and some are Ruby related. 1) This is concerning displaying error messages. I am assuming

I have added an authenticator using the instructions here: http://wiki.rubyonrails.org/rails/pages/HowtoAuthenticate The LoginController sets session["employee"] to an employee. When i try to access the session["employee"] from another controller i get this error : " TypeError (no marshal_dump is defined for class OraNumber): c:/ruby/lib/ruby/1.8/pstore.rb:159:in `dump''...

I have gone through the following site for the creation of my login page: To mention I am using Windows XP pfofessional running on WEBBrick server http://wiki.rubyonrails.com/rails/pages/HowtoAuthenticate The code is given in the following 3 steps: 1)The controller that needs protection: class WeblogController < ActionController::Base before_filter :authenticate def index # show the secret stuff end protected def authenticate unless @session["person"]...