HORIZON HASKELLDocslts/ghc-10.0.xfc4e5982026-10-11Search names, modules, packages, or :: a typeCtrl K

GHC 10.0.0.20260917 · lts/ghc-10.0.x · fc4e598 · 2026-10-11

Modulehoauth2-2.15.2Haskell2010

Network.OAuth2.AuthorizationRequest

Bindings Authorization part of The OAuth 2.0 Authorization Framework RFC6749 https://www.rfc-editor.org/rfc/rfc6749

  • 2 types
  • 2 values
  • Packagehoauth2-2.15.2
  • Exports4
  • LanguageHaskell2010
  • LicenceMIT
  • SourceAuthorizationRequest.hs

Authorization Request Errors

2 declarations

Authorization Code Grant Error Responses https://tools.ietf.org/html/rfc6749#section-4.1.2.1

I found it hard to figure out a way to test the authorization error flow. When anything goes wrong in an /authorize request, it gets stuck at the provider page, hence no way for this library to parse error response. In other words, /authorize ends up with 4xx or 5xx. Revisit this whenever you find a case where an OAuth2 provider redirects back to the relying party with errors.

Instances3Eq, Show, FromJSON
Instances3Eq, Show, FromJSON

URLs

2 declarations