Re: Bearer token authentication?

2018-03-04 Thread Daniel Stenberg 

On Fri, 2 Mar 2018, John Hascall wrote:


Has any thought been given to the possibility of something along these
lines:

curl_easy_setopt(curl, CURLOPT_HTTPAUTH, CURLAUTH_BEARER);
curl_easy_setopt(curl, CURLOPT_BEARER_TOKEN, token);


You mean like @LEW21 made this PR?

  https://github.com/curl/curl/pull/2102

... I wouldn't mind some feedback on that proposal!

--

 / daniel.haxx.se
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html

Bearer token authentication?

2018-03-02 Thread John Hascall 
Has any thought been given to the possibility of something along these
lines:


curl_easy_setopt(curl, CURLOPT_HTTPAUTH, CURLAUTH_BEARER);
curl_easy_setopt(curl, CURLOPT_BEARER_TOKEN, token);

   *or*
curl_easy_setopt(curl, CURLOPT_PASSWORD, token);


because faffing around in the struct curl_slist of headers to
​ ​
replace the "Authorization Bearer *token*" header every time you have
​ ​
a new token
(especially with short-lived tokens like at api.box.com)
​ ​
is annoying
​ (and
smells of an abstraction violation).

Or am I missing some sane way to do it?


John​
---
Unsubscribe: https://cool.haxx.se/list/listinfo/curl-library
Etiquette:   https://curl.haxx.se/mail/etiquette.html