{"push_id":550854945,"size":1,"distinct_size":1,"ref":"refs/heads/jwt-bearer","head":"b7f638f7c9b84595a40f2e28ddc0f5c4c8da10dd","before":"262b75e5faa5ee31cb4805744c35bf1e36695283","commits":[{"sha":"b7f638f7c9b84595a40f2e28ddc0f5c4c8da10dd","author":{"email":"28c4723fc4f18c9264197ab693cc29746fd1c3a5@hypothes.is","name":"Randall Leeds"},"message":"JWT Bearer token support\n\nChange the authorization code to normalize the annotator auth tokens\nand headers into standard JWT bearer tokens and the auth token header\ninto the HTTP Authorization header.\n\nStart accepting JWT Bearer tokens as authorization grants. When used\nin this manner, the issuing client must already be authorized for the\nsubject. Currently, the only valid issuer is the built-in web client,\nwhich is always pre-authorized. In the future, it will be necessary to\nstore validations in a database and only allow the JWT Bearer Token\nflow generate tokens for users that have already completed another\nflow with the client that allows for the use of refresh tokens. In\nessence, the JWT Bearer Token is a self-issued, pre-authorized refresh\ntoken when used as an authorization grant.","distinct":true,"url":"https://api.github.com/repos/hypothesis/h/commits/b7f638f7c9b84595a40f2e28ddc0f5c4c8da10dd"}]}