You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think the authentication via header should be like github's curl -H "Authorization: token OAUTH-TOKEN" https://api.github.com rather than what doorkeepers currently is curl -H "Authorization: OAUTH-TOKEN" https://api.github.com. Changing it will allow basic/digest auth etc....
Github probably uses an extension of access token.
We already accept header authorization via Bearer token, which is defined in section 7.1. This is also compatible with the oauth2 gem (if you use the defaults).
Not sure if it makes sense to change this right now. However, access token extensibility is definitely one of the features we should add in the future.
I think the authentication via header should be like github's
curl -H "Authorization: token OAUTH-TOKEN" https://api.github.com
rather than what doorkeepers currently iscurl -H "Authorization: OAUTH-TOKEN" https://api.github.com
. Changing it will allow basic/digest auth etc....source: http://developer.github.com/v3/
The text was updated successfully, but these errors were encountered: