eeva/servant
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Replace User with Account in Generalized Authentication section (#757)

Browse source 
* Change `User` to `Account` in Generalized Authentication section
This commit is contained in:
Ryan James Spencer 2017-10-17 23:31:29 +11:00 committed by Alp Mestanogullari
parent 602806296e
commit ff5502f4f7
1 changed files with 17 additions and 14 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
doc/tutorial/Authentication.lhs
View file

@ -245,25 +245,28 @@ your feedback!
### What is Generalized Authentication? ### What is Generalized Authentication?
**TL;DR**: you throw a tagged `AuthProtect` combinator in front of the endpoints **TL;DR**: you throw a tagged `AuthProtect` combinator in front of the
you want protected and then supply a function `Request -> Handler user` endpoints you want protected and then supply a function `Request -> Handler a`,
which we run anytime a request matches a protected endpoint. It precisely solves where `a` is the type of your choice representing the data returned by
the "I just need to protect these endpoints with a function that does some successful authentication - e.g., a `User` or, in our example below, `Account`.
complicated business logic" and nothing more. Behind the scenes we use a type This function is run anytime a request matches a protected endpoint. It
family instance (`AuthServerData`) and `Context` to accomplish this. precisely solves the "I just need to protect these endpoints with a function
that does some complicated business logic" and nothing more. Behind the scenes
we use a type family instance (`AuthServerData`) and `Context` to accomplish
this.
### Generalized Authentication in Action ### Generalized Authentication in Action
Let's implement a trivial authentication scheme. We will protect our API by Let's implement a trivial authentication scheme. We will protect our API by
looking for a cookie named `"servant-auth-cookie"`. This cookie's value will looking for a cookie named `"servant-auth-cookie"`. This cookie's value will
contain a key from which we can lookup a `User`. contain a key from which we can lookup a `Account`.
```haskell ```haskell
-- | A user type that we "fetch from the database" after -- | An account type that we "fetch from the database" after
-- performing authentication -- performing authentication
newtype Account = Account { unAccount :: Text } newtype Account = Account { unAccount :: Text }
-- | A (pure) database mapping keys to users. -- | A (pure) database mapping keys to accounts.
database :: Map ByteString Account database :: Map ByteString Account
database = fromList [ ("key1", Account "Anne Briggs") database = fromList [ ("key1", Account "Anne Briggs")
, ("key2", Account "Bruce Cockburn") , ("key2", Account "Bruce Cockburn")
@ -279,7 +282,7 @@ lookupAccount key = case Map.lookup key database of
``` ```
For generalized authentication, servant exposes the `AuthHandler` type, For generalized authentication, servant exposes the `AuthHandler` type,
which is used to wrap the `Request -> Handler user` logic. Let's which is used to wrap the `Request -> Handler Account` logic. Let's
create a value of type `AuthHandler Request Account` using the above `lookupAccount` create a value of type `AuthHandler Request Account` using the above `lookupAccount`
method: method:
@ -377,13 +380,13 @@ forward:
1. use the `AuthProtect` combinator to protect your API. 1. use the `AuthProtect` combinator to protect your API.
2. choose a application-specific data type used by your server when 2. choose a application-specific data type used by your server when
authentication is successful (in our case this was `User`). authentication is successful (in our case this was `Account`).
3. Create a value of `AuthHandler Request User` which encapsulates the 3. Create a value of `AuthHandler Request Account` which encapsulates the
authentication logic (`Request -> Handler User`). This function authentication logic (`Request -> Handler Account`). This function
will be executed everytime a request matches a protected route. will be executed everytime a request matches a protected route.
4. Provide an instance of the `AuthServerData` type family, specifying your 4. Provide an instance of the `AuthServerData` type family, specifying your
application-specific data type returned when authentication is successful (in application-specific data type returned when authentication is successful (in
our case this was `User`). our case this was `Account`).
Caveats: Caveats: