delta/python-packages/oauthlib.git/tests/oauth1, branch python-3.7

Fix OIDC tests (#565)

2018-09-20T22:10:17+00:00

* Unmute ignored OIDC tests.

* Fix more import errors.

* Remove recently invalidated test for id_token_hint.

* Fix tested grants.

* Fix import on py27.

Correct recent merge (#596)

2018-09-14T19:58:16+00:00

Merge c8a7cb199a8d448c2934100a5bb06598be402939 mistakenly reverted a
line from aef9a3e944f41c3afaaf22ba20f86a267a7d3bb3.

Remove unnecessary workaround for bytes type

2018-09-14T12:18:10+00:00

The type 'bytes' is available on all supported Pythons. Likewise the
byte literal b'...' is available on all supported Pythons. Use idiomatic
Python and remove workaround for an issue that no longer exists. Makes
the code more forward compatible with Python 3.

Add support for HMAC-SHA256 (builds on PR#388) (#498)

2017-11-14T15:44:44+00:00

* Add support for HMAC-SHA256

* Add explicit declaration of HMAC-SHA1 and point HMAC at it

To avoid confusion, HMAC constant name should explicitly state which SHA variant is used, but for backwards compatibility, SIGNATURE_HMAC is still needed

* add support for HMAC-SHA256 including tests and comments

* constructor tests verify client built with correct signer method

Sorted imports.

2017-09-17T11:14:31+00:00

Replace all uses of assertEquals with assertEqual

2017-04-16T20:57:30+00:00

assertEquals is deprecated in favor of assertEqual.

When running tests, fixes warnings of the form:

  DeprecationWarning: Please use assertEqual instead.

For more information, see:

https://docs.python.org/3/library/unittest.html#deprecated-aliases

adding validator_log to store what the endpoint computed

2015-08-12T16:37:21+00:00

Check for rsa_key when it's actually needed

2015-05-07T03:12:47+00:00

Support newer PyJWT (1.0.0). remove PyCrypto completely for cryptography and PyJWT helpers. Reformat some test certificates to be easier to maintain. Update documentation to match use of cryptography instead of PyCrypto

2015-04-14T16:30:44+00:00

Create Signature Only OAuth1 Endpoint

2014-09-11T16:31:58+00:00

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.