Include WWW-Authenticate headers for invalid_client. Closes #33

See: http://tools.ietf.org/html/rfc6749#section-5.2
Add missing test for cfdadcf3
2.0.1
Fix casing in examples. Closes #38 and #40
Fix continueAfterResponse implentation + add tests (ref 65836456)
2.0.2
Update changelog. Closes #42
Modified Authorization Grant to accept a GET with parameters in the Query String

The RFC Spec for OAuth 2 specifies that the Authorization Grant endpoint be
a HTTP GET.  POST is allowed to be supported, but GET must be implemented
according to the spec.
This change modifies authCodeGrant.js to look for the appropriate parameters
in either the query string or the body, so HTTP GET and HTTP POST are both
supported.

Added tests to test/authCodeGrant.js to test both POST and GET functionality.
Closes #56
Added note on running postgres example. Closes #46
Add client_credentials grant_type support. Closes #36
v2.1.0
fixed conversion
Merge pull request #59 from dcartertwo/master

Typo
Support custom loggers
Added ability for client to have multiple redirect URIs which are valid.

The OAuth 2 spec envisions that an individual client can have several redirect URIs that are valid for a given clientId.  This change allows the redirect_uri returned from the model to be either a string or an array.  Added test for an invalid URI when multiple URIs are returned.  Also added tests for valid URIs when either a string or an Array is returned from getClient.
Made modifications based on pull request feedback:

* Using Array.isArray() to determine if client.redirectUri is an array
* Modified names of some tests for consistency
Merge pull request #65 from mjsalinger/multipleRedirectURIs

Added ability for client to have multiple redirect URIs which are valid.
Fix continueAfterResponse when granting (+test case). Closes #66
2.1.1
Using typeof keyword instead of function