Merge pull request #9 from siacomuzzi/master

Minor Enhancements

README.md

@@ -1,3 +1,5 @@
+> Fix for Yammer's new authentication method ([issue #3](https://github.com/jaredhanson/passport-yammer/issues/3)), which needs the auth token specified in an Authorization: Bearer <xxx> header. Credits to [oscarrenalias](https://github.com/oscarrenalias).
+
 # Passport-Yammer
 
 [Passport](https://github.com/jaredhanson/passport) strategy for authenticating

lib/passport-yammer/strategy.js

@@ -50,6 +50,11 @@ function Strategy(options, verify) {
   this.name = 'yammer';
   this._userProfileURL = options.userProfileURL || 'https://www.yammer.com/api/v1/users/current.json';
 
+  // Fix for Yammer's new authentication method, which needs the auth token specified
+  // in an Authorization: Bearer <xxx> header. Luckily Passport's OAuth2 client has support for
+  // this built-in so it's only a matter of enabling it
+  this._oauth2.useAuthorizationHeaderforGET(true);
+
   // Despite claiming to support the OAuth 2.0 specification, Yammer's
   // implementation does anything but.  Yammer's token endpoint returns a
   // response that is so non-conformant that we are forced to resort to

package.json

@@ -1,6 +1,6 @@
 {
   "name": "passport-yammer",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "Yammer authentication strategy for Passport.",
   "keywords": ["passport", "yammer", "auth", "authn", "authentication", "identity"],
   "repository": {
@@ -22,7 +22,7 @@
   "main": "./lib/passport-yammer",
   "dependencies": {
     "pkginfo": "0.2.x",
-    "passport-oauth": "0.1.x"
+    "passport-oauth": "1.x.x"
   },
   "devDependencies": {
     "vows": "0.6.x"