OAuth2 authentication for yesod
Go to file
patrick brisbin bbda0d2f47 Support injecting fetchAccessToken
hoauth2's fetchAccessToken provides credentials in the Authorization
header, while fetchAccessToken2 provides them in that header but also
the POST body.

It was discovered that some providers only support one or the other, so
using fetchAccessToken2 would be preferred since it should work with
either. This happened in #129.

However, we discovered at least one provider (Okta) that actively
rejects requests unless they're supplying credentials in exactly one
place:

    Cannot supply multiple client credentials. Use one of the following:
    credentials in the Authorization header, credentials in the post
    body, or a client_assertion in the post body."

This patch reverts back to fetchAccessToken, but makes it possible to
for client to use fetchAccessToken2 if necessary via alternative
functions.
2020-12-10 15:20:31 -05:00
.circleci Drop CI support for ghc-8.4 2020-08-24 10:49:14 -04:00
example Add WordPress.com as an auth provider 2020-08-19 10:57:14 -04:00
src Support injecting fetchAccessToken 2020-12-10 15:20:31 -05:00
test Project setup files 2018-01-23 10:16:22 -05:00
.env.example Add WordPress.com to .env.example 2020-08-19 10:57:14 -04:00
.gitignore Bring back example application 2018-02-13 08:59:01 -05:00
.hlint.yaml Address HLint issues 2018-01-23 10:16:22 -05:00
.stylish-haskell.yaml Project setup files 2018-01-23 10:16:22 -05:00
CHANGELOG.md Version bump 2020-09-04 16:57:47 -04:00
LICENSE Correct license information 2018-01-26 13:58:16 -05:00
Makefile Add setup.tools to Makefile 2020-08-24 10:49:14 -04:00
package.yaml Version bump 2020-09-04 16:57:47 -04:00
README.md Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00
Setup.lhs Initial import 2013-07-14 11:11:44 +02:00
stack-lts-13.2.yaml Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00
stack-lts-13.2.yaml.lock Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00
stack-lts-16.10.yaml fixup! Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00
stack-lts-16.10.yaml.lock fixup! Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00
stack-nightly.yaml Fix nightly build 2020-08-19 10:56:37 -04:00
stack-nightly.yaml.lock Compile on nightly/ghc-8.8 2019-12-03 20:27:15 -05:00
stack.yaml Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00
stack.yaml.lock Update to latest GHC, Stackage resolver, hoauth2 2020-08-24 10:49:14 -04:00

Yesod.Auth.OAuth2

OAuth2 AuthPlugins for Yesod.

Usage

import Yesod.Auth
import Yesod.Auth.OAuth2.GitHub

instance YesodAuth App where
    -- ...

    authPlugins _ = [oauth2GitHub clientId clientSecret]

clientId :: Text
clientId = "..."

clientSecret :: Text
clientSecret = "..."

Some plugins, such as GitHub and Slack, have scoped functions for requesting additional information:

oauth2SlackScoped [SlackBasicScope, SlackEmailScope] clientId clientSecret

Working with Extra Data

We put the minimal amount of user data possible in credsExtra -- just enough to support you parsing or fetching additional data yourself.

For example, if you work with GitHub and GitHub user profiles, you likely already have a model and a way to parse the /user response. Rather than duplicate all that in our library, we try to make it easy for you to re-use that code yourself:

authenticate creds = do
    let
        -- You can run your own FromJSON parser on the response we already have
        eGitHubUser :: Either String GitHubUser
        eGitHubUser = getUserResponseJSON creds

        -- Avert your eyes, simplified example
        Just accessToken = getAccessToken creds
        Right githubUser = eGitHubUser

    -- Or make followup requests using our access token
    runGitHub accessToken $ userRepositories githubUser

    -- Or store it for later
    insert User
        { userIdent = credsIdent creds
        , userAccessToken = accessToken
        }

NOTE: Avoid looking up values in credsExtra yourself; prefer the provided get functions. The data representation itself is no longer considered public API.

Local Providers

If we don't supply a "Provider" (e.g. GitHub, Google, etc) you need, you can write your own using our provided Prelude:

import Yesod.Auth.OAuth2.Prelude

pluginName :: Text
pluginName = "mysite"

oauth2MySite :: YesodAuth m => Text -> Text -> AuthPlugin m
oauth2MySite clientId clientSecret =
    authOAuth2 pluginName oauth2 $ \manager token -> do
        -- Fetch a profile using the manager and token, leave it a ByteString
        userResponse <- -- ...

        -- Parse it to your preferred identifier, e.g. with Data.Aeson
        userId <- -- ...

        -- See authGetProfile for the typical case

        pure Creds
            { credsPlugin = pluginName
            , credsIdent = userId
            , credsExtra = setExtra token userResponse
            }
  where
    oauth2 = OAuth2
        { oauthClientId = clientId
        , oauthClientSecret = Just clientSecret
        , oauthOAuthorizeEndpoint = "https://mysite.com/oauth/authorize"
        , oauthAccessTokenEndpoint = "https://mysite.com/oauth/token"
        , oauthCallback = Nothing
        }

The Prelude module is considered public API, though we may build something higher-level that is more convenient for this use-case in the future.

Development & Tests

stack setup
stack build --dependencies-only
stack build --pedantic --test

Please also run HLint and Weeder before submitting PRs.


CHANGELOG | LICENSE