A Django application for running one or more SAML service providers (SP).
Local Test Application
Start the local SimpleSAML IdP
docker run -it --rm -p 8080:8080 -p 8443:8443 \ -e SIMPLESAMLPHP_SP_ENTITY_ID=http://localhost:8000/sso/local/ \ -e SIMPLESAMLPHP_SP_ASSERTION_CONSUMER_SERVICE=http://localhost:8000/sso/local/acs/ \ -e SIMPLESAMLPHP_SP_SINGLE_LOGOUT_SERVICE=http://localhost:8000/sso/local/logout/ \ kristophjunge/test-saml-idp
Bootstrap and run the local SP test app
python manage.py migrate python manage.py bootstrap python manage.py runserver
AUTHENTICATION_BACKENDS- By default the Django authentication system is used to authenticate and log in users. Add
AUTHENTICATION_BACKENDSsetting to authenticate using Django's
Usermodel. The user is looked up using
User.USERNAME_FIELDmatching the SAML
nameid, and created if it doesn't already exist. See the Field Mapping section below for how to map SAML attributes to
LOGIN_REDIRECT_URL- This is the URL users will be redirected to by default after a successful login (or verification). Optional if you set
IdP.login_redirector specify a
nextparameter in your login URL.
SESSION_SERIALIZER- By default, Django uses
django.contrib.sessions.serializers.JSONSerializer, which does not allow for setting specific expiration dates on sessions. If you want to use the
IdP.respect_expirationflag to let the IdP dictate when the Django session should expire, you should change this to
django.contrib.sessions.serializers.PickleSerializer. But if you do not plan on using that feature, leave the default.
The application comes with a URLconf that can be included:
sso prefix as above, and assuming an IdP slug of
idp, the following URLs will be available:
||The entity ID, and metadata URL. Visiting this will produce metadata XML you can give to the IdP administrator.|
||The Assertion Consumer Service (ACS). This is what the IdP will POST to upon a successful login.|
||URL to trigger the login sequence for this IdP. Available programmatically as
||URL to trigger an IdP login and display a test page containing all the SAML attributes passed back. Available programmatically as
||URL to trigger a verification sequence for this IdP. Available programmatically as
Configuring an identity provider (IdP)
- Create an
IdPmodel object, either via the Django admin or programmatically. If you have metadata from your IdP, you can enter the URL or XML now, but it is not required yet.
- Generate a certificate to use for SAML requests between your SP and this IdP. You may use the built-in admin action for this by going to the Django admin page for Identity Providers, checking the row(s) you want, and selecting "Generate certificates" from the Action dropdown. If you already have a certificate you want to use, you can paste it into the appropriate fields.
- Give your IdP administrator the Entity ID/Metadata URL and ACS URL, if they need to explicitly allow access or provide you attributes.
- At this point, if you didn't in step 1, you'll need to enter either the IdP metadata URL, or metadata XML directly. Saving will automatically trigger an import of the IdP metadata, so you should see the Last Import date update if successful. There is also an "Import metadata" admin action to trigger this manually.
Your IdP is now ready for testing. On the admin page for your IdP object, there is a "Test IdP" button in the upper right corner. You can also visit the
/sso/idp/test/ URL manually to initiate a test. A successful test of the IdP will show a page containing the NameID and SAML attributes provided by the IdP.
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
|Filename, size||File type||Python version||Upload date||Hashes|
|Filename, size django_saml_sp-0.3.0-py3-none-any.whl (16.7 kB)||File type Wheel||Python version py3||Upload date||Hashes View hashes|
|Filename, size django-saml-sp-0.3.0.tar.gz (11.3 kB)||File type Source||Python version None||Upload date||Hashes View hashes|
Hashes for django_saml_sp-0.3.0-py3-none-any.whl