Drf-httpsig

Latest version: v1.2.0

Safety actively analyzes 613797 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

1.2.0

--------------------

* Updated to support and require httpsig 1.x.
* Switched to pytest over nose

1.1.0

--------------------

* Updated to support and require httpsig 1.1.
* Updated requirements to simply Django<1.7 and DRF<3.0. Last version for those, I suspect.

1.0.2

--------------------

* Updated authentication return value to set request.auth to the key_id used.

1.0.1

--------------------

* Added/verified Python 3 support and tests (3.2+).
* Added support for sending a DRF authorization challenge if we're the primary authenticator.
* Switched to using the `httpsig` HeaderVerifier instead of doing it ourselves. Lots of code got deleted there.
* Changed fetch_user_data to also receive the algorithm the keyID is for.
* Updated README.
* Removed models.py -- the client should handle that part entirely.

1.0b2

--------------------------

* Added versioneer.
* Updated requirements to use latest httpsig.
* Added "setup.py test" and tox support.
* Fixed a unit test.

1.0b1

--------------------

* Renamed to drf-httpsig because I don't hate my hands.
* Updated requirements versions to be more sane.
* Switched to a different branch for http_signature.
* Removed API_KEY_HEADER in favor of the keyId, per spec.
* Cleaned up the repo a bit.
* Cleaned up the code a bit.


djangorestframework-httpsignature (previous)
============================================

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.