The servant-auth-token package

[ Tags: bsd3, library, web ] [ Propose Tags ]

Please see README.md


[Skip to Readme]

Properties

Versions 0.1.0.0, 0.1.1.0, 0.1.2.0, 0.2.0.0, 0.2.0.1, 0.3.0.0, 0.3.1.0, 0.3.2.0, 0.4.0.0, 0.4.1.0, 0.4.1.1, 0.4.2.0, 0.4.3.0, 0.4.4.0, 0.4.4.1, 0.4.5.0, 0.4.6.0, 0.4.7.0, 0.4.7.1, 0.5.0.0 (info)
Change log CHANGELOG.md
Dependencies aeson-injector (>=1.0.4 && <1.1), base (>=4.8 && <5), bytestring (==0.10.*), containers (==0.5.*), http-api-data (>=0.3.5 && <0.4), mtl (==2.2.*), pwstore-fast (==2.4.*), servant (==0.11.*), servant-auth-token-api (>=0.4.2 && <0.5), servant-server (==0.11.*), text (==1.2.*), time (>=1.5 && <1.7), transformers (>=0.4 && <0.6), uuid (==1.3.*), wai (==3.2.*) [details]
License BSD3
Copyright 2016-2017 Anton Gushcha
Author Anton Gushcha <ncrashed@gmail.com> , Ivan Lazar Miljenovic <Ivan.Miljenovic@gmail.com>
Maintainer ncrashed@gmail.com
Category Web
Home page https://github.com/ncrashed/servant-auth-token#readme
Source repository head: git clone https://github.com/ncrashed/servant-auth-token
Uploaded Tue Aug 29 21:21:35 UTC 2017 by NCrashed
Distributions NixOS:0.5.0.0
Downloads 791 total (43 in the last 30 days)
Rating 0.0 (0 ratings) [clear rating]
  • λ
  • λ
  • λ
Status Docs available [build log]
Last success reported on 2017-08-29 [all 1 reports]
Hackage Matrix CI

Modules

[Index]

Downloads

Maintainer's Corner

For package maintainers and hackage trustees


Readme for servant-auth-token-0.5.0.0

[back to package description]

servant-auth-token

Build Status

The repo contains server implementation of servant-auth-token-api.

How to add to your server

At the moment you have two options for backend storage:

  • persistent backend - persistent backend, simple to integrate with your app.

  • acid-state backend - acid-state backend is light solution for in memory storage, but it is more difficult to integrate it with your app.

  • Possible candidates for other storage backends: VCache, leveldb, JSON files. To see how to implement them, see HasStorage type class.

Now you can use 'guardAuthToken' to check authorization headers in endpoints of your server:

-- | Read a single customer from DB
customerGet :: CustomerId -- ^ Customer unique id
  -> MToken '["customer-read"] -- ^ Required permissions for auth token
  -> ServerM Customer -- ^ Customer data
customerGet i token = do
  guardAuthToken token
  runDB404 "customer" $ getCustomer i