mirror of https://github.com/golang-jwt/jwt.git
adjust documentation
This commit is contained in:
parent
80dccb9209
commit
0db2f42ba9
14
parser.go
14
parser.go
|
@ -215,13 +215,13 @@ func (p *Parser) DecodeSegment(seg string) ([]byte, error) {
|
||||||
return encoding.DecodeString(seg)
|
return encoding.DecodeString(seg)
|
||||||
}
|
}
|
||||||
|
|
||||||
// Parse parses, validates, verifies the signature and returns the parsed token.
|
// Parse parses, validates, verifies the signature, and returns the parsed token.
|
||||||
// keyFunc will receive the parsed token and should return the cryptographic key
|
// When a keyFunc is set and a tokenString is provided, the library will not accept
|
||||||
// for verifying the signature. The caller is strongly encouraged to set the
|
// the 'none' type algorithm, ensuring security by default. However, it is strongly
|
||||||
// WithValidMethods option to validate the 'alg' claim in the token matches the
|
// recommended to explicitly specify the allowed algorithms using the WithValidMethods
|
||||||
// expected algorithm. For more details about the importance of validating the
|
// option to ensure the 'none' type algorithm is definitively rejected. For more
|
||||||
// 'alg' claim, see
|
// information on the importance of validating the 'alg' claim, see
|
||||||
// https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/
|
// https://auth0.com/blog/critical-vulnerabilities-in-json-web-token-libraries/.
|
||||||
func Parse(tokenString string, keyFunc Keyfunc, options ...ParserOption) (*Token, error) {
|
func Parse(tokenString string, keyFunc Keyfunc, options ...ParserOption) (*Token, error) {
|
||||||
return NewParser(options...).Parse(tokenString, keyFunc)
|
return NewParser(options...).Parse(tokenString, keyFunc)
|
||||||
}
|
}
|
||||||
|
|
Loading…
Reference in New Issue