Re: bearer token authorization with HTTPS transport
- From
brian m. carlson <sandals@crustytoothpaste.net>
- Date
- Jan 6, 2015, 02:41 UTC
- Message-ID
- <20150106024123.GF1025060@vauxhall.crustytoothpaste.net>
- In-Reply-To
- <20141231014209.GA8789@peff.net>
On Tue, Dec 30, 2014 at 08:42:10PM -0500, Jeff King wrote:
Show 8 quoted lines
>Another option would be to just teach the credential code to accept a >"bearer" field from a credential helper. We would need to: > > 1. Teach the credential code that getting a "bearer" token is > sufficient (it does not need to prompt for username/password). > > 2. Teach the http code to pull the bearer field out and stick it in an > "Authorization" header.
For the benefit of someone trying to implement this, libcurl has the CURLOPT_XOAUTH2_BEARER option. It does requires libcurl 7.33, though.
-- brian m. carlson / brian with sandals: Houston, Texas, US +1 832 623 2791 | http://www.crustytoothpaste.net/~bmc | My opinion only OpenPGP: RSA v4 4096b: 88AC E9B2 9196 305B A994 7552 F1BA 225C 0223 B187