Modulehoauth2-2.14.3Haskell2010

Network.OAuth2.Experiment.Flows.UserInfoRequest

1 class
2 values

Packagehoauth2-2.14.3
Exports3
LanguageHaskell2010
LicenceMIT
SourceUserInfoRequest.hs

classclass HasUserInfoRequest (a :: k)

Instances4HasUserInfoRequest

HasUserInfoRequest AuthorizationCodeApplicationDefined in hoauth2-2.14.3 · Network.OAuth2.Experiment.Grants.AuthorizationCode
HasUserInfoRequest DeviceAuthorizationApplicationDefined in hoauth2-2.14.3 · Network.OAuth2.Experiment.Grants.DeviceAuthorization
HasUserInfoRequest JwtBearerApplicationDefined in hoauth2-2.14.3 · Network.OAuth2.Experiment.Grants.JwtBearer
HasUserInfoRequest ResourceOwnerPasswordApplicationDefined in hoauth2-2.14.3 · Network.OAuth2.Experiment.Grants.ResourceOwnerPassword

valueconduitUserInfoRequest

:: (MonadIO m, HasUserInfoRequest a, FromJSON b)
=> IdpApplication i a
-> Manager
-> AccessToken
-> ExceptT ByteString m b

Standard approach of fetching /userinfo

valueconduitUserInfoRequestWithCustomMethod

:: (MonadIO m, HasUserInfoRequest a, FromJSON b)
=> Manager -> AccessToken -> URI -> ExceptT ByteString m b
-> IdpApplication i a
-> Manager
-> AccessToken
-> ExceptT ByteString m b

Usually conduitUserInfoRequest is good enough. But some IdP has different approach to fetch user information rather than GET. This method gives the flexiblity.