Hackage :: [Package]

yesod-auth-account: An account authentication plugin for Yesod

[ library, mit, web ] [ Propose Tags ] [ Report a vulnerability ]

An auth plugin for accounts. Each account consists of a username, email, and password. The plugin provides new account, email verification, and password reset pages that can be customized to enhance the user experience.

[Skip to Readme]

Downloads

Maintainer's Corner

Package maintainers

For package maintainers and hackage trustees

Candidates

  • No Candidates
Versions [RSS] 1.1.0, 1.1.0.1, 1.2.0, 1.2.1, 1.2.2, 1.2.3, 1.2.4, 1.2.5, 1.2.6, 1.4.0, 1.4.1, 1.4.2, 1.4.3
Change log Changelog.md
Dependencies base (>=4 && <5), blaze-html (>=0.6), bytestring (>=0.10), mtl (>=2.1), nonce (>=1.0), persistent (>=1.3), pwstore-fast (>=2.0), text (>=0.11), yesod-auth (>=1.2), yesod-core (>=1.2), yesod-form (>=1.3), yesod-persistent (>=1.2) [details]
License MIT
Author John Lenz <lenz@math.uic.edu>
Maintainer John Lenz <lenz@math.uic.edu>
Category Web
Home page https://bitbucket.org/wuzzeb/yesod-auth-account
Source repo head: hg clone https://bitbucket.org/wuzzeb/yesod-auth-account
Uploaded by JohnLenz at 2016-08-28T20:19:07Z
Distributions
Reverse Dependencies 1 direct, 0 indirect [details]
Downloads 10100 total (8 in the last 30 days)
Rating (no votes yet) [estimated by Bayesian average]
Your Rating
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2016-08-28 [all 1 reports]

Readme for yesod-auth-account-1.4.3

[back to package description]

This package provides a Yesod authentication plugin for accounts. Each account consists of an username, email, and password. When initially creating an account, the email is verified by sending a link in an email. The plugin also supports password reset via email.

The plugin provides default pages implementing all of this functionality, but it has been designed to allow all the pages (new account page, password reset, etc.) to be customized or for the forms to be embedded into your own pages allowing you to just ignore the routes inside the plugin. The details are contained in the haddock documentation.

The plugin supports any form data storage by requiring you to implement a couple of interfaces for data access. The plugin has instances of these interfaces using persistent, but you can create your own implementation if you are not using persistent or want more control over user data access and storage.

A complete working example using persistent is example.hs. Also, see the haddock documentation.