7 Commits

Author	SHA1	Message	Date
David Komer	0ebbeab74c	conversion error fixed	2016-03-17 15:12:22 +02:00
David Komer	52e4189627	use json.Number for claims check ... if parser.UseJSONNumber is true then the Claims[“exp”] and Claims[“nbf”] can be full int64 range, not limited to float64 vnbf and vexp are just flags for whether or not the values were obtained through either method and should be checked	2016-03-17 15:00:13 +02:00
Snorre lothar von Gohren Edwin	ca46641b15	PR updated, faster string method and more reasonable message feedback	2015-12-23 09:43:00 +01:00
Snorre lothar von Gohren Edwin	57b1269c41	modifications on PR. Added a space in the bearer string check so that we unexpectly dont experience an base64url encoding because bearer is technically part of a valid endcoding, we think. Also moved it into a failed decoding to get a better feedback for the developer, but not do unessecary amount of string checks	2015-12-22 15:30:57 +01:00
Dave Grijalva	b728399c73	signature should be populated after parsing a valid token	2015-11-16 12:42:37 -08:00
Dave Grijalva	774f319043	added tests for parser. fixed parser when using restricted method list	2015-11-02 15:22:08 -08:00
Dave Grijalva	bdfe8ca0b6	created a Parser type to allow for non-global parser configuration	2015-10-29 11:45:16 -07:00