A very minimal SAML 2.0 SP implementation for modern Python versions.
This library is not meant to be a full-featured SAML 2.0 implementation, but to provide a minimal, robust implementation without too many dependencies.
It has successfully been tested against:
- Google Workspace SAML
- Keycloak 12.0.4
- Okta
- Microsoft Azure AD
- Please note that when using the federationmetadata.xml URL for metadata,
you will need to specify your app's
appidin the URL in order for Azure to supply the correct key material needed to validate the signature. IOW,https://login.microsoftonline.com/TENANTID/federationmetadata/2007-06/federationmetadata.xml?appid=APPID. Eliding theappidparameter will make things not work.
- Please note that when using the federationmetadata.xml URL for metadata,
you will need to specify your app's
The package is available on PyPI.
pip install smolsamlIn addition, you will need the xmlsec (aka xmlsec1) utility,
as to avoid a dependency on lxml and python-xmlsec (which can be a pain to install and may conflict with
one another due to libxml version requirements).
- On Debian/Ubuntu, this can be installed with
apt install xmlsec1. - On macOS, this can be installed with
brew install libxmlsec1.
We'll go ahead and assume you've chosen to use some sort of web framework (the library doesn't care).
The steps to authenticate a user are:
- Construct an
SPConfigurationthat describes your application. The values need to match what you've configured in your IdP, and naturally the ACS URL will need to be hooked up somehow in your web framework. - Construct an
IDPConfiguration; the easiest way to do this isIDPConfiguration.from_metadata_xml. (You'll need to have fetched the metadata yourself, the library doesn't care how you do that.) - Call
initiate_login; you'll get aRedirectobject, which describes where you'll want to whisk the user off to. - The user will authenticate with the IdP, and then be redirected back to your ACS URL.
- In your ACS endpoint, read the
SAMLResponsePOST parameter. Callprocess_saml_responsewith it, and your configuration objects. This will raise an exception if the data is not valid. If it is valid, you'll get aSAMLResponseobject back, which contains the user's attributes. It probably will be a good idea to try to disallow multipleSAMLResponses with the same ID; that sounds like a replay attack.
- π This library hasn't been tested against any IdPs other than the ones listed above. If you have a different IdP and it works, please let me know!
- π This library doesn't support practically any optional SAML 2.0 feature.
- π Not all claims that should probably be checked are currently checked.
- Authentication request signing is currently not supported. However, happily, most IdPs don't require it.
smolsaml is distributed under the terms of the MIT license.