Flask-dance

------------------
* Flask-Dance no longer checks for the existence of a ``X-Forwarded-Proto``
header to determine if generated URLs should use a ``https://`` scheme.
If you are running your application behind a TLS termination proxy,
use Werkzeug's ``ProxyFix`` middleware to inform Flask of that.

------------------
* Added the Dropbox pre-set configuration
* Added the Meetup pre-set configuration
* Added the Facebook pre-set configuration
* Flask-Dance now always passes the optional ``redirect_uri`` parameter to
the OAuth 2 authorization request, since Dropbox requires it.
* Make Flask-Dance provide additional information in errors when providers fail
to provide auth tokens

------------------
* Make the ``authorized`` property on both ``OAuth1Session`` and ``OAuth2Session``
dynamically load the token from the backend

------------------
* Redesigned token storage backend system: it now uses objects

.. warning::
This release is not backwards-compatible, due to the changes to how backends
work. If you are using the SQLAlchemy backend, read the documentation to see
how it works now!

* Added documentation about OAuth protocol
* Added quickstarts for Google, and for a multi-user SQLAlchemy system
* Added ``reprompt_consent`` parameter to Google pre-set configuration
* Added ``oauth_error`` signal
* If there is an error with the OAuth 2 authorization process, Flask-Dance
will now redirect the user anyway rather than letting the error bubble up
and cause a 500 status code. The ``oauth_error`` signal will be fired
with information about the error.

------------------
* ``OAuth2ConsumerBlueprint`` now accepts two new arguments to its constructor:
``authorization_url_params`` and ``token_url_params``
* When using the Google pre-set configuration, you can now request offline
access for your OAuth token by passing ``offline=True`` to the
``make_google_blueprint`` function

------------------
* Added ``anon_user`` argument to ``set_token_storage_sqlalchemy()`` method
* Fire ``oauth_authorized`` signal before setting token, so that a signal
handler can set the logged-in user
* You can now indicate that an OAuth token should not be stored by returning
``False`` from any receiver function that is connected to the
``oauth_authorized`` signal