Community maintained clone of https://github.com/dgrijalva/jwt-go
Go to file
Dave Grijalva 652b4be28c make helper methods more specific 2014-08-26 14:24:20 -07:00
cmd/jwt pass keys as interface{} rather than []byte 2014-08-26 14:14:17 -07:00
test Added support for HS384 and HS512 signing methods 2014-07-05 15:08:42 -07:00
.gitignore a useful example app 2014-05-19 20:13:39 -07:00
LICENSE mit license 2012-04-18 12:02:05 -07:00
README.md removed 2.0 release notice from readme 2014-08-26 13:47:03 -07:00
VERSION_HISTORY.md make helper methods more specific 2014-08-26 14:24:20 -07:00
doc.go updating documentation 2014-06-15 19:39:12 -07:00
hmac.go pass keys as interface{} rather than []byte 2014-08-26 14:14:17 -07:00
hmac_test.go Added support for HS384 and HS512 signing methods 2014-07-05 15:08:42 -07:00
jwt.go cleanup and documentation updates 2014-08-26 14:18:59 -07:00
jwt_test.go pass keys as interface{} rather than []byte 2014-08-26 14:14:17 -07:00
rsa.go make helper methods more specific 2014-08-26 14:24:20 -07:00
rsa_test.go make helper methods more specific 2014-08-26 14:24:20 -07:00
rsa_utils.go make helper methods more specific 2014-08-26 14:24:20 -07:00
signing_method.go pass keys as interface{} rather than []byte 2014-08-26 14:14:17 -07:00

README.md

A go (or 'golang' for search engine friendliness) implementation of JSON Web Tokens

What the heck is a JWT?

In short, it's a signed JSON object that does something useful (for example, authentication). It's commonly used for Bearer tokens in Oauth 2. A token is made of three parts, separated by .'s. The first two parts are JSON objects, that have been base64url encoded. The last part is the signature, encoded the same way.

The first part is called the header. It contains the necessary information for verifying the last part, the signature. For example, which encryption method was used for signing and what key was used.

The part in the middle is the interesting bit. It's called the Claims and contains the actual stuff you care about. Refer to the RFC for information about reserved keys and the proper way to add your own.

What's in the box?

This library supports the parsing and verification as well as the generation and signing of JWTs. Current supported signing algorithms are RSA256 and HMAC SHA256, though hooks are present for adding your own.

Parse and Verify

Parsing and verifying tokens is pretty straight forward. You pass in the token and a function for looking up the key. This is done as a callback since you may need to parse the token to find out what signing method and key was used.

	token, err := jwt.Parse(myToken, func(token *jwt.Token) ([]byte, error) {
		return myLookupKey(token.Header["kid"])
	})

	if err == nil && token.Valid {
		deliverGoodness("!")
	} else {
		deliverUtterRejection(":(")
	}

Create a token

	// Create the token
	token := jwt.New(jwt.GetSigningMethod("HS256"))
	// Set some claims
	token.Claims["foo"] = "bar"
	token.Claims["exp"] = time.Now().Add(time.Hour * 72).Unix()
	// Sign and get the complete encoded token as a string
	tokenString, err := token.SignedString(mySigningKey)

Project Status & Versioning

This library is considered production ready. Feedback and feature requests are appreciated. The API should be considered stable. There should be very few backwards-incompatible changes outside of major version updates (and only with good reason).

This project uses Semantic Versioning 2.0.0. Accepted pull requests will land on master. Periodically, versions will be tagged from master. You can find all the releases on the project releases page.

More

Documentation can be found on godoc.org.

The command line utility included in this project (cmd/jwt) provides a straightforward example of token creation and parsing as well as a useful tool for debugging your own integration. For a more http centric example, see this gist.