Security Advisories (1)
CPANSA-Jifty-2011-01 (2011-03-17)

The path as passed in the fragment request data structure was used verbatim in the dispatcher and other locations. This possibly allowed requests to walk around ACLs by requesting '/some/safe/place/../../../dangerous' as a fragment.

NAME

Jifty::Plugin::Authentication::Password::Action::Login - process login with password

new

arguments

Return the email and password form fields

validate_email ADDRESS

Makes sure that the email submitted is a legal email and that there's a user in the database with it.

Overridden from Jifty::Action::Record.

validate_username ADDRESS

there's a user in the database with it.

Overridden from Jifty::Action::Record.

validate_password PASSWORD

Makes sure that the password submitted actually exists, unless there's a token and a hashed password.

Overridden from Jifty::Action::Record.

validate_token TOKEN

Make sure we issued the token within the last 30 seconds, otherwise time out the request.

take_action

Actually check the user's password. If it's right, log them in. Otherwise, throw an error.

load_user

Load up and return a YourApp::User object for the user trying to log in

login_message $user_object

Returns the "hi, you're logged in message"