misc-deps
/
inth-oauth2
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

optionally pass credentials in request body

This commit is contained in:
Konstantin Stepanov 2016-01-26 00:50:14 +03:00
parent 3be25b6e6c
commit 22123533ba
2 changed files with 12 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
src/client/mod.rs
View File

@ -154,6 +154,11 @@ impl<P: Provider> Client<P> {
body_pairs.push(("redirect_uri", redirect_uri)); body_pairs.push(("redirect_uri", redirect_uri));
} }
if P::credentials_in_body() {
body_pairs.push(("client_id", &self.client_id));
body_pairs.push(("client_secret", &self.client_secret));
}
let json = try!(self.post_token(body_pairs)); let json = try!(self.post_token(body_pairs));
let token = try!(P::Token::from_response(&json)); let token = try!(P::Token::from_response(&json));
Ok(token) Ok(token)

7
src/provider.rs
View File

@ -19,6 +19,13 @@ pub trait Provider {
/// ///
/// See [RFC 6749, section 3.2](http://tools.ietf.org/html/rfc6749#section-3.2). /// See [RFC 6749, section 3.2](http://tools.ietf.org/html/rfc6749#section-3.2).
fn token_uri() -> &'static str; fn token_uri() -> &'static str;
/// Provider supports credentials via request body only.
/// Although not recommended by the RFC, some implementations accept client_id
/// and client_secret as a part of request only (most notable offender is vk.com).
///
/// See [RFC 6749, section 2.3.1](http://tools.ietf.org/html/rfc6749#section-2.3.1).
fn credentials_in_body() -> bool { false }
} }
/// Google OAuth 2.0 provider. /// Google OAuth 2.0 provider.