> On March 7, 2017, 12:33 a.m., Greg Mann wrote: > > 3rdparty/libprocess/include/process/jwt.hpp > > Lines 42 (patched) > > <https://reviews.apache.org/r/56667/diff/6/?file=1656686#file1656686line42> > > > > Should we also provide a link to RFC-7515 here?
IMO we shouldn't. While RFC 7519 and RFC 7515 are closely related, only RFC 7519 covers JWT and mentions RFC 7515 where it is necessary. - Jan ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/56667/#review168040 ----------------------------------------------------------- On March 6, 2017, 3:53 p.m., Jan Schlicht wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/56667/ > ----------------------------------------------------------- > > (Updated March 6, 2017, 3:53 p.m.) > > > Review request for mesos, Alexander Rojas and Greg Mann. > > > Bugs: MESOS-7001 > https://issues.apache.org/jira/browse/MESOS-7001 > > > Repository: mesos > > > Description > ------- > > JSON Web Tokens can be used to create claim-based access tokens and is > typically used for HTTP authentication. > This implementation is intended for internal use, e.g. Mesos is supposed > to only parse tokens that it also created. It doesn't fully comply with > RFC 7519. Currently the only supported cryptographic algorithm is HMAC > with SHA-256. > > > Diffs > ----- > > 3rdparty/libprocess/Makefile.am 75386184108214e67a58c328258ec204099d638c > 3rdparty/libprocess/include/process/jwt.hpp PRE-CREATION > 3rdparty/libprocess/src/jwt.cpp PRE-CREATION > 3rdparty/libprocess/src/tests/jwt_tests.cpp PRE-CREATION > > > Diff: https://reviews.apache.org/r/56667/diff/6/ > > > Testing > ------- > > make check > > > Thanks, > > Jan Schlicht > >