Changelog for yesod-auth-oauth2-0.7.0.2

Unreleased

v0.7.0.2

Add Auth0 provider (@hw202207)

v0.7.0.1

Support hoauth-2.2 and 2.3

v0.7.0.0

Support hoauth2-2.0

The OAuth2 type's fields have changed. If you are not defining your own Local Providers (i.e. you're not constructing any OAuth2 values) you should not be affected by this change. If you are, you should update to the new field names.

v0.6.3.4

Remove dependencies upper bounds

v0.6.3.1

Relax dependencies bounds

v0.6.3.0

Expose onDispatchError and generic OtherDispatchError for passthrough log
Don't throw exceptions; handle all errors through the set-message-redirect path
Respect onErrorHtml for said error-handling
Support custom widget in Google plugin @jmorag

v0.6.2.3

Allow bytestring-0.11 and cryptonite 0.28
Test with GHC 8.10 on CI

v0.6.2.2

Consistent dependencies bounds in all targets

v0.6.2.1

Adjust lower bounds on cryptonite

v0.6.2.0

Filter + from state tokens

This decreases entropy in the token slightly, but ensures that providers performing unexpected +/space/%20 encoding (e.g. ClassLink) still function.

See #140.
Add ClassLink provider

v0.6.1.7

Relax upper bounds on hoauth2 and http-client

v0.6.1.6

Revert back to Authorization-header-only fetchAccessToken function
Add authOAuth2' and authOAuth2Widget', which use fetchAccessToken2

v0.6.1.5

Update to GHC-8.8, and hoauth2-1.14
Drop CI-backed support for GHC-8.4

v0.6.1.4

Tighten upper bound on hoauth2

v0.6.1.3

Replace System.Random state token generation with cryptonite
Allow aeson-1.5 and hoauth2-1.14
Add WordPress.com provider @nbloomf

v0.6.1.2

Don't report our own errors like OAuth2 ErrorResponses

v0.6.1.1

Added AzureAD provider
COMPATIBILITY: Use hoauth2-1.8.1
COMPATIBILITY: Test with GHC 8.6.3, and not 8.2

v0.6.1.0

Allow http-client-0.6

v0.6.0.0

Remove deprecated Github module

v0.5.3.0

Allow aeson-1.4 and hoauth2-1.8

v0.5.2.0

InvalidProfileResponse was replaced with different, situation-specific constructors; the exception type is considered internal API, but end-users may see them in logs, or if they (unexpectedly) escape our error-handling
Errors during log-in no longer result in 4XX or 5XX responses; they now redirect to LoginR with the exception details logged and something user-appropriate displayed via setMessage

v0.5.1.0

Added GitLab provider
Added properly-named GitHub module, deprecated Github
Store refreshToken in credsExtra

v0.5.0.0

COMPATIBILITY: Allow and require yesod-1.6
COMPATIBILITY: Stop testing GHC 8.0 on CI

v0.4.1.0

Check for errors in callback query params, as described in the spec

v0.4.0.1

COMPATIBILITY: Allow http-types-0.12

v0.4.0.0

COMPATIBILITY: Allow aeson-1.3
COMPATIBILITY: Dropped a lot of information from credsExtra:

TL;DR: you'll no longer find things like username or email as keys in the credsExtra map. Instead, you'll find the encoded profile response we received and the OAuth access token. You can/should do your own decoding or make your own follow-up requests to get extra data about your users.

This reduced a lot of complexity, likely duplication between our decoding and yours, and (I think) makes the library easier to use.
- Issue
- PR
COMPATIBILITY: Support GHC-8.2
COMPATIBILITY: Drop (claimed, but never tested) support for GHC-7.8 & 7.10
LICENSE: fixed vague licensing (MIT now)