go-jose alternatives and similar packages
Based on the "Authentication & OAuth" category
4.9 0.0 go-jose VS authbossA modular authentication system for the web. It tries to remove as much boilerplate and "hard things" as possible so that each time you start a new web project in Go, you can plug it in, configure, and start building your app without having to build an authentication system each time.
Do you think we are missing an alternative of go-jose or a related project?
Disclaimer: This library contains encryption software that is subject to the U.S. Export Administration Regulations. You may not export, re-export, transfer or download this code or any part of it in violation of any United States law, directive or regulation. In particular this software may not be exported or re-exported in any form or on any media to Iran, North Sudan, Syria, Cuba, or North Korea, or to denied persons or entities mentioned on any US maintained blocked list.
The implementation follows the
JSON Web Encryption (RFC 7516),
JSON Web Signature (RFC 7515), and
JSON Web Token (RFC 7519) specifications.
Tables of supported algorithms are shown below. The library supports both
the compact and full serialization formats, and has optional support for
multiple recipients. It also comes with a small command-line utility
for dealing with JOSE messages in a shell.
Note: We use a forked version of the
encoding/json package from the Go
standard library which uses case-sensitive matching for member names (instead
of case-insensitive matching).
This is to avoid differences in interpretation of messages between go-jose and
libraries in other languages.
All new feature development takes place on the
master branch, which we are
preparing to release as version 3 soon. Version 2 will continue to receive
critical bug and security fixes. Note that starting with version 3 we are
using Go modules for versioning instead of
gopkg.in as before.
Version 1 (on the
v1 branch) is frozen and not supported anymore.
See below for a table of supported algorithms. Algorithm identifiers match the names in the JSON Web Algorithms standard where possible. The Godoc reference has a list of constants.
|Key encryption||Algorithm identifier(s)|
|AES key wrap||A128KW, A192KW, A256KW|
|AES-GCM key wrap||A128GCMKW, A192GCMKW, A256GCMKW|
|ECDH-ES + AES key wrap||ECDH-ES+A128KW, ECDH-ES+A192KW, ECDH-ES+A256KW|
1. Not supported in multi-recipient mode
|Signing / MAC||Algorithm identifier(s)|
|RSASSA-PKCS#1v1.5||RS256, RS384, RS512|
|RSASSA-PSS||PS256, PS384, PS512|
|HMAC||HS256, HS384, HS512|
|ECDSA||ES256, ES384, ES512|
2. Only available in version 2 of the package
|Content encryption||Algorithm identifier(s)|
|AES-CBC+HMAC||A128CBC-HS256, A192CBC-HS384, A256CBC-HS512|
|AES-GCM||A128GCM, A192GCM, A256GCM|
|DEFLATE (RFC 1951)||DEF|
Supported key types
See below for a table of supported key types. These are understood by the
library, and can be passed to corresponding functions such as
NewSigner. Each of these keys can also be wrapped in a JWK if desired, which
allows attaching a key id.
|ECDH, ECDSA||*ecdsa.PublicKey, *ecdsa.PrivateKey|
1. Only available in version 2 or later of the package
Examples can be found in the Godoc
reference for this package. The
subdirectory also contains a small command-line utility which might be useful
as an example as well.
*Note that all licence references and agreements mentioned in the go-jose README section above are relevant to that project's source code only.