Release history and notes¶
Sequence based identifiers are used for versioning (schema follows below):
major.minor[.revision]
- It’s always safe to upgrade within the same minor version (for example, from 0.3 to 0.3.4).
- Minor version changes might be backwards incompatible. Read the release notes carefully before upgrading (for example, when upgrading from 0.3.4 to 0.4).
- All backwards incompatible changes are mentioned in this document.
1.6.12¶
2018-12-25
- Additions to the Django contrib app. Added additional callback
USER_VALIDATE_CALLBACK
to the authentication backends which is fired right after the signature validation to allow custom logic to the incoming authentication requests.
1.6.11¶
2018-12-20
- Additions to the Django contrib app mainly. Authentication backend has
been made customisable. Most of the code is moved to the
BaseSkaAuthenticationBackend
. Introduced new authentication backendSkaAuthenticationConstanceBackend
to be used in combination withdjango-constance
.
1.6.10¶
2018-12-16
- Fixes in the callbacks import of the Django contrib app.
- Testing shell commands; minor fixes in tests.
1.6.8¶
2018-12-03
Note
Release dedicated to Charles Aznavour.
- Django 2.0 and 2.1 compatibility.
- Upgrade test suite.
- Fixes in docs.
- Python 3.4 is removed from support matrix (however, it might still work).
1.6.1¶
2016-12-03
- Fixes in tests of django-ska package.
- Add shell.py command for easy debugging.
- Minor fixes.
- Clean up docs.
1.6¶
2016-12-02
- Django 1.8, 1.9 and 1.10 compatibility.
- pep8 fixes.
- The
six
package requirement increased to six >= 1.9. - Drop support of Django < 1.8 (it still may work, but no longer guaranteed).
- Drop support of Python 2.6.x.
- Fix broken Django authentication backend, due to deprecation of
request.REQUEST
.
1.5¶
2014-06-04
- Introducing abstract signature class in order to make it possible to define more hash algorithms.
- Added HMAC MD5, HMAC SHA-224, HMAC SHA-256, HMAC SHA-384 and HMAC SHA-512 hash algorythms. HMAC SHA-1 remains a default.
1.4.3¶
2014-02-28
- The
ValidationResult
class is slightly changed. Thereason
property is replaced witherrors
(whilereason
is left mainly for backwards compatibility). For getting human readable message you’re encouraged to use themessage
property (string) instead of joining strings manually. Additionally, each error got a separate object (seeerror_codes
module):INVALID_SIGNATURE
andSIGNATURE_TIMESTAMP_EXPIRED
. - Minor documentation improvements.
1.4.2¶
2013-12-25
- Minor fixes.
- Added authentication backend tests.
- Added tumpering tests.
- Minor documentation improvements.
1.4.1¶
2013-12-23
- Armenian, Dutch and Russian translations added for Django app.
- Documentation improved.
1.4¶
2013-12-21
- Providers concept implemented. It’s now possible to handle multiple secret keys and define custom callbacks and redirect URLs per provider. See the docs for more.
- Better example project.
- Better documentation.
1.3¶
2013-12-21
- Make it possible to add additional data to the signed request by providing
an additional
extra
argument. - Reflect the new functionality in Django app.
- Better documentation.
1.2¶
2013-12-17
- Optionally storing the authentication tokens into the database, when used with Django auth backend.
- Optionally checking, if signature token has already been used to log into Django. If so, ignoring the login attempt. A management command is added to purge old signature data.
- Demo (quick installer) added.
1.1¶
2013-12-14
- Class based views validation decorator added.
- Authentication backend for Django based on authentication tokens generated
with
ska
.