silvermine / apigateway-utils

100%

master: 99%

LAST BUILD ON BRANCH jwt_validation_utility

branch: jwt_validation_utility

CHANGE BRANCH

x

Reset

• jwt_validation_utility
• add_request_logging
• alb-support
• allow_custom_resp_builder_classes_in_handler
• errors_and_jwt_validation
• fix_17_mime_with_params
• fix_22_requestid_logging
• fix_options_jwt_request
• fix_response_builder_export
• headers_and_bodies
• inherit_content_type_exports
• jwt_secured_request
• master
• new-error-format
• no_console_rule
• npm-updates
• onebytegone_grab_bag
• prepare_0.10.0
• prepare_v0.9.0
• stop_caching_errors_and_non_gets
• syntactic_response_helpers
• v0.10.0
• v0.10.1
• v0.11.0
• v0.12.0
• v0.12.1
• v0.12.2
• v0.9.0

Build # 44

Build Type

push

travis-ci

Committed by jthomerson

Commit Message

BREAKING: Expose JWT validation, change validateAuthorizationHeader

This commit exposes JWT validation as a utility, but in doing so also introduces a
**breaking change** that allows `JWTSecuredRequest.validateAuthorizationHeader` to return
multiple errors.

The format before was:

```
{ isValid: true }
// or:
{ isValid: false, msg: 'User-visible message', err: 'More details for developer' }
```

The format now is:

```
{ errors: [], token: {} }; // (token is the decoded JWT object)
// or:
{
   errors: [ { msg: 'User-visible message', err: 'More details for developer' } ],
   token: {},
}
```

In this new format: there may be multiple errors; Also, token is the decoded JWT, and is
undefined if the JWT could not be decoded.

Run Details

211 of 211 relevant lines covered (100.0%)

49.05 hits per line