Create a new user from just a username and password

May throw a DuplicateLogin if given username is not unique

Check whether a user with the given username exists.

Create or update a given user

May throw a BackendError if something goes wrong.

Destroy the given user

May throw a BackendError if something goes wrong.

Lookup a user by her username, check given password and perform login

Remember user from the remember token if possible and perform login

Login and persist the given AuthUser in the active session

Meant to be used if you have other means of being sure that the person is who she says she is.

Logout the active user

Return the current user; trying to remember from cookie if possible.

Convenience wrapper around rememberUser that returns a bool result

Mutate an AuthUser, marking successful authentication

This will save the user to the backend.

Mutate an AuthUser, marking failed authentication

This will save the user to the backend.

Authenticate and log the user into the current session if successful.

This is a mid-level function exposed to allow roll-your-own ways of looking up a user from the database.

This function will:

1. Check the password
2. Login the user into the current session
3. Mark success/failure of the authentication trial on the user record

Abstract data type holding all necessary information for auth operation

All storage backends need to implement this typeclass

Backend operations may throw BackendErrors

Authetication settings defined at initialization time

Default settings for Auth.

 asMinPasswdLen = 8
 asRememberCookieName = "_remember"
 asRememberPeriod = Just (2*7*24*60*60) = 2 weeks
 asLockout = Nothing
 asSiteKey = "site_key.txt"

Type representing the concept of a User in your application.

Default AuthUser that has all empty values.

Internal representation of a User. By convention, we demand that the application is able to directly fetch a User using this identifier.

Think of this type as a secure, authenticated user. You should normally never see this type unless a user has been authenticated.

Password is clear when supplied by the user and encrypted later when returned from the db.

Authentication failures indicate what went wrong during authentication. They may provide useful information to the developer, although it is generally not advisable to show the user the exact details about why login failed.

This will be replaced by a role-based permission system.

Run a function on the backend, and return the result.

This uses an existential type so that the backend type doesn't escape AuthManager. The reason that the type is Handler b (AuthManager v) a and not a is because anything that uses the backend will return an IO something, which you can liftIO, or a Handler b (AuthManager v) a if it uses other handler things.

Check password for a given user.

Returns Nothing if check is successful and an IncorrectPassword error otherwise

Set a new password for the given user. Given password should be clear-text; it will be encrypted into a Encrypted.

Register a new user by specifying login and password Param fields

A MonadSnap handler that processes a login form.

The request paremeters are passed to performLogin

Simple handler to log the user out. Deletes user from session.

Require that an authenticated AuthUser is present in the current session.

This function has no DB cost - only checks to see if a user_id is present in the current session.

Add all standard auth splices to a Heist-enabled application.

This adds the following splices: <ifLoggedIn> <ifLoggedOut>

A splice that can be used to check for existence of a user. If a user is present, this will run the contents of the node.

 <ifLoggedIn> Show this when there is a logged in user </ifLoggedIn>

A splice that can be used to check for absence of a user. If a user is not present, this will run the contents of the node.

 <ifLoggedOut> Show this when there is a logged in user </ifLoggedOut>