The secrets module should be used for generating cryptographically
strong random numbers suitable for managing data such as passwords,
account authentication, security tokens, and related secrets.

In particularly, secrets should be used in preference to the default
pseudo-random number generator in the random module, which is
designed for modelling and simulation, not security or cryptography.

(cherry picked from commit d21fd53)

* Added sphinx build for developers

Rationale is to build docs locally to prevent RTD to break later.

* Replace manual sphinx into make

* Renamed idan URL to oauthlib community

* Renamed http into https URLs since http is returning 302

* python requests library renamed its home URL

* Add ignore list for "make linkcheck"

linkcheck is doing requests to github with anonymous access, however creating an issue require an logged-in account

* virtualenv changed its homepage and website.

* Fixed broken link

(cherry picked from commit 32e5ad1)

Fixed grammar on line 7.

fix method params and clarify oauth_protected

In certain cases a provider may wish to verify the signature of an
oauth request without doing anything more with it. Learning Tools
Interoperability (LTI), for example, uses "0-legged OAuth" for it's
signature verification process.

http://www.imsglobal.org/lti/
http://andyfmiller.com/2013/02/10/does-lti-use-oauth/

This adds a new ``SignatureOnlyEndpoint`` that implements only the
client validation and signature verification, and leaves off the other
parts that would need to be validated.

django-oauth-tools doesn't seem to support oauth1.