jwt: JSON Web Token (JWT) decoding and encoding
JSON Web Token (JWT) is a compact URL-safe means of representing claims to be transferred between two parties.
To get started, see the documentation for the Web.JWT module.
[Skip to Readme]
Downloads
- jwt-0.10.1.tar.gz [browse] (Cabal source package)
- Package description (as included in the package)
Maintainer's Corner
For package maintainers and hackage trustees
Candidates
| Versions [RSS] | 0.1.0, 0.1.1, 0.2.0, 0.2.1, 0.3.0, 0.4.0, 0.4.1, 0.4.2, 0.4.3, 0.4.4, 0.5.0, 0.5.1, 0.5.2, 0.5.3, 0.6.0, 0.7.0, 0.7.1, 0.7.2, 0.8.0, 0.9.0, 0.10.0, 0.10.1, 0.11.0 |
|---|---|
| Change log | CHANGELOG.md |
| Dependencies | aeson (>=0.7), base (>=4.8 && <5), bytestring (>=0.10), containers (>=0.5), cryptonite (>=0.6), http-types (>=0.8), memory (>=0.8), network-uri, scientific (>=0.2), semigroups (>=0.15.4), text (>=0.11), time (>=1.1), unordered-containers (>=0.2), vector (>=0.7.1), x509, x509-store [details] |
| License | MIT |
| Author | Brian McKenna |
| Maintainer | brian@brianmckenna.org |
| Category | Web |
| Home page | https://bitbucket.org/puffnfresh/haskell-jwt |
| Bug tracker | https://bitbucket.org/puffnfresh/haskell-jwt/issues |
| Source repo | head: git clone https://bitbucket.org/puffnfresh/haskell-jwt.git |
| Uploaded | by puffnfresh at 2021-12-02T10:52:35Z |
| Distributions | Debian:0.10.0, LTSHaskell:0.11.0, NixOS:0.11.0, Stackage:0.11.0 |
| Reverse Dependencies | 20 direct, 20 indirect [details] |
| Downloads | 24788 total (116 in the last 30 days) |
| Rating | 1.75 (votes: 2) [estimated by Bayesian average] |
| Your Rating | |
| Status | Docs available [build log] Last success reported on 2021-12-02 [all 1 reports] |
Readme for jwt-0.10.1
[back to package description]Haskell JSON Web Token (JWT)
JSON Web Token (JWT) is a compact URL-safe means of representing claims to be transferred between two parties.
From http://self-issued.info/docs/draft-ietf-oauth-json-web-token.html
JSON Web Token (JWT) is a compact URL-safe means of representing claims to be transferred between two parties. The claims in a JWT are encoded as a JavaScript Object Notation (JSON) object that is used as the payload of a JSON Web Signature (JWS) structure or as the plaintext of a JSON Web Encryption (JWE) structure, enabling the claims to be digitally signed or MACed and/or encrypted.
See the Web.JWT module documentation to get started.
