52
92%
master: 89%

Ran 24 Jun 2015 03:14PM UTC

Jobs 8

Files 1

Run time 2min

Badge

Embed ▾

pending completion

Build # 52

Build Type

push

travis-ci

Committed by

leejo

Commit Message

resolve #2 - sign tokens

use Mojo::JWT to generate the auth codes and tokens returned by the
plugin. this means they are signed with the jwt_secret, a new and
required config setting for the plugin, so can be decoded for the
users to inspect the scopes and client

in theory this means we can validate auth codes and tokens without
a database lookup[1], however it isn't that straightforward as the
JWT is currently lacking the information about the user and using
JWTs without a db lookup makes revoking of tokens slightly more
difficult[2]

[1] which would make using the plugin in its most basic form both
persistent and multi process compatible

[2] https://auth0.com/blog/2015/03/10/blacklist-json-web-token-api-keys/

Run Details

158 of 173 relevant lines covered (91.33%)

56.91 hits per line

Jobs

ID	Job ID	Ran	Coverage
1	52.1	24 Jun 2015 03:16PM UTC	5.56	Travis Job 52.1
2	52.2	24 Jun 2015 03:17PM UTC	5.56	Travis Job 52.2
3	52.3	24 Jun 2015 03:14PM UTC	95.76	Travis Job 52.3
4	52.4	24 Jun 2015 03:14PM UTC	95.76	Travis Job 52.4
5	52.5	24 Jun 2015 03:14PM UTC	95.76	Travis Job 52.5
6	52.6	24 Jun 2015 03:15PM UTC	95.76	Travis Job 52.6
7	52.7	24 Jun 2015 03:15PM UTC	95.76	Travis Job 52.7
8	52.8	24 Jun 2015 03:15PM UTC	95.76	Travis Job 52.8

Source Files on build 52

Detailed source file information is not available for this build.

leejo / mojolicious-plugin-oauth2-server / 52
92%
master: 89%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 52

leejo / mojolicious-plugin-oauth2-server / 52 92% master: 89%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Jobs

Source Files on build 52

leejo / mojolicious-plugin-oauth2-server / 52
92%
master: 89%

README BADGES
x