Path to this page:
./
www/p5-Mojo-JWT,
JSON Web Token the Mojo way
Branch: CURRENT,
Version: 0.09nb2,
Package name: p5-Mojo-JWT-0.09nb2,
Maintainer: pkgsrc-usersJSON Web Token is described in https://tools.ietf.org/html/rfc7519.
Mojo::JWT implements that standard with an API that should feel
familiar to Mojolicious users (though of course it is useful
elsewhere). Indeed, JWT is much like Mojolicious::Sessions except
that the result is a url-safe text string rather than a cookie.
In JWT, the primary payload is called the claims, and a few claims
are reserved, as seen in the IETF document. The header and the
claims are signed when stringified to guard against tampering. Note
that while signed, the data is not encrypted, so don't use it to
send secrets over clear channels.
Master sites: (Expand)
Filesize: 15.676 KB
Version history: (Expand)
- (2024-11-16) Updated to version: p5-Mojo-JWT-0.09nb2
- (2023-07-06) Updated to version: p5-Mojo-JWT-0.09nb1
- (2023-04-29) Updated to version: p5-Mojo-JWT-0.09
- (2023-02-27) Package added to pkgsrc.se, version p5-Mojo-JWT-0.08 (created)
CVS history: (Expand)
2023-07-06 11:43:03 by Thomas Klausner | Files touched by this commit (2483) |
Log message:
*: recursive bump for perl 5.38
|
2023-07-03 14:38:42 by Thomas Klausner | Files touched by this commit (1) |
Log message:
p5-Mojo-JWT: fix DEPENDS line
|
2023-04-29 16:53:44 by Wen Heping | Files touched by this commit (2) |
Log message:
Update to 0.09
Update DEPENDS
Upstream changes:
0.09 2020-11-22
- Allow passing in a JWKSet which can be used for decoding/verifying tokens \
(ccakes)
|
2023-02-27 19:00:43 by Nikita | Files touched by this commit (3) |
Log message:
www/p5-Mojo-JWT: import as p5-Mojo-JWT version 0.08
Import from wip, packaged by coypu.
JSON Web Token is described in https://tools.ietf.org/html/rfc7519.
Mojo::JWT implements that standard with an API that should feel
familiar to Mojolicious users (though of course it is useful
elsewhere). Indeed, JWT is much like Mojolicious::Sessions except
that the result is a url-safe text string rather than a cookie.
In JWT, the primary payload is called the claims, and a few claims
are reserved, as seen in the IETF document. The header and the
claims are signed when stringified to guard against tampering. Note
that while signed, the data is not encrypted, so don't use it to
send secrets over clear channels.
|