v0.7.2: Database-backed configuration

[0.7.2] - 2020-04-14

Many thanks for major contributions (especially on the testing front where the project was lacking) from Amertz08 and askvortsov1

Added

• Major and breaking change: Service Providers are now backed by the database instead of being configured via the settings: #51
• Test coverage has been improved significantly. CI was added to run tests, linting and report code coverage which will improve stability of development.
• Django 3.0 is added to the tests matrix. We currently are doing Python 3.6, 3.7, 3.8 and Django 2.2, 3.0.

Removed

• Dropped Python 3.5.
• Django 2.0 and 2.1 as they are no longer officially supported Django versions.

v0.6.3 bugfix release

[0.6.3] - 2020-02-10

Bugfix release, thanks to contributions from pix666 in #61

v0.6.2 bugfix release

Bugfix release, thanks to contributions from @mjholtkamp in #54, #55, and #56

v0.5.0

• The user identifier attribute is now customizable via the SAML_IDP_DJANGO_USERNAME_FIELD settings. #20
• Supports the HTTP REDIRECT binding. #20
• Bugfix in the NameID generation where destination instead of entity ID was used. #18

BREAKING CHANGE: the has_access(user) method on the Processor class has been changed to has_access(request). This to allow a broader scope of access control checks to perform. If you have subclassed the BaseProcessor class and have overriden this method with a custom implementation, you will need to change this.