This package provides an OpenID Connect 1.0 compliant interface for clients and some useful types and functions for providers. The primary goals of this package are security and usability. To get started, take a look at the OpenID.Connect.Client.Flow.AuthorizationCode module.

library, network, Propose Tags , OpenID.Connect.Authentication, OpenID.Connect.Client.DynamicRegistration, OpenID.Connect.Client.Flow.AuthorizationCode, OpenID.Connect.Client.Provider, OpenID.Connect.Provider.Key, OpenID.Connect.Scope, OpenID.Connect.TokenResponse, jose, certifying, OpenID Connect Core, OpenID Connect Discovery, The OAuth 2.0 Authorization Framework (RFC6749), JSON Web Token (RFC7519), JSON Web Signature (RFC7515), JSON Web Key (RFC7517), haskell, openid-connect
cabal install openid-connect



OpenID Connect 1.0 in Haskell

An OpenID Connect 1.0 compliant library written in Haskell.

The primary goals of this package are security and usability.

Client Features

This library mostly focuses on the client side of the OpenID Connect protocol.

Supported flows:

  • Authorization Code (see OpenID.Connect.Client.Flow.AuthorizationCode) (§3.1)
  • Implicit (partial implementation, patches welcome) (§3.2)
  • Hybrid (partial implementation, patches welcome) (§3.3)

Significant features:

  • ID Token validation via the jose library (§2)
  • Additional OIDC claim validation (e.g., nonce, azp, etc.) (§2)
  • Full support for all defined forms of client authentication (§9)
  • Handles session cookie generation and validation (§, §15.5.2)
  • Dynamic Client Registration 1.0.

Provider Features

Some utility types and functions are available to assist in the writing of an OIDC Provider:

  • Discovery document (OpenID Connect Discovery 1.0 §3)
  • Key generation (simple wrapper around jose)

Certification Status

We plan on fully certifying this implementation using the following profiles:

  • Basic Relying Party
  • Implicit Relying Party
  • Hybrid Relying Party
  • Relying Party Using Configuration Information
  • Dynamic Relying Party
  • Form Post Relying Party

Specifications and RFCs