This package provides support for SAML2 based on ``pyxb``.
``pyxb`` (http://pypi.python.org/pypi/PyXB) generates a Python class
collection for an XML schema and provides means to convert between
associated Python instances and xml documents. It is used to generate
and parse SAML2 messages.
The package adds support for digital signatures and SAML2 bindings and
metadata management.
Dependencies
============
PyXB
----
Class collections generated by ``pyxb`` tend to be very version dependent.
Thus, they must usually be regenerated when the ``pyxb`` version has changed.
The current package's version mostly uses class collections from
the ``wssplat`` and ``saml20`` bundles of ``pyxb``. Thus, they
have a good chance to be updated together with ``pyxb``.
However, the ``pyxb`` ``saml2`` bundle lacks support for
the so called SAML2 context classes. This package contains
class collections generated with ``pyxb==1.1.4``. They need to
be regenerated if the ``pyxb`` version changes (and you use those classes --
which is not very likely).
The ``gen.sh`` script in subpackage ``pyxb``
can provide clues how to regenerate them.
The original ``PyXB`` author (Peter A. Bigot) has
`abandoned the project <https://github.com/pabigot/pyxb/blob/next/README.md>`_.
The latest release ``1.2.6`` is no longer compatible with modern
Python versions (at least from ``Python 3.10`` on).
To handle this situation, ``dm.saml2`` no longer declares the ``PyXB``
dependency in its ``setup.py``. This allows the use a ``PyXB`` replacement,
potentially named differently.
If you want to use ``dm.saml2`` with Python 3.10+, you must provide
such a replacement.
I have not yet found a ``Python 3.10`` compatible replacement with
the required ``wssplat`` and ``saml20`` bundles.
For a customer project, I used the following approach:
I started with the `PyXB-CTC 1.3.0 source distribution <https://pypi.org/project/pyxb-ctc/>`_, fixed there a few remaining ``Python 3.10`` incompatibilities (essentially replacing references to ``collections`` by corresponding ones to ``collections.abc``) and generated the missing ``wssplat`` and ``saml20`` bundles.
dm.xmlsec.binding
-----------------
Check its installation notes should you face related installation problems.
Example
=======
This section provides a simple example on how to create, sign and
verify an assertion with this package.
Always ensure, the ``xmlsec`` library is initialized. Otherwise, it signing/
signature verification can fail with dubious messages.
>>> import dm.xmlsec.binding as xmlsec
>>> xmlsec.initialize()
We now build an assertion as Python object.
>>> import pyxb.binding.datatypes as xs
>>> from dm.saml2.pyxb.assertion import (NameID, Assertion, Subject, \
... AuthnStatement, AttributeStatement, AuthnContext, AuthnContextClassRef, \
... Attribute, AttributeValue, \
... CreateFromDocument
... )
>>> from datetime import datetime
>>>
>>> issuer = NameID('http://bfd.de')
>>> ass = Assertion(issuer)
>>>
>>> subject = Subject(NameID('Dieter Maurer'))
>>>
>>> ass.Subject = subject
>>>
>>> authn = AuthnStatement(
... None,
... AuthnContext(AuthnContextClassRef('urn:oasis:names:tc:SAML2:2.0:ac:classes:Password')),
... AuthnInstant=datetime.utcnow(),
... )
>>>
>>> ass.AuthnStatement.append(authn)
>>>
>>> att = AttributeStatement(
... # does not yet work perfectly -- needs further analysis
... Attribute(xs.string('Dieter', _element=AttributeValue), Name='Firstname'),
... Attribute(xs.string('Maurer', _element=AttributeValue), Name='Lastname'),
... )
>>>
>>> ass.AttributeStatement.append(att)
Now it looks like this (not yet signed).
>>> unsigned_ass = ass.toxml()
>>> print unsigned_ass
<?xml version="1.0" ?><ns1:Assertion ID="_fb6dc6ac-9ee6-4a1f-8010-6dba6e0d9746" IssueInstant="2012-07-06T07:24:53.262859" Version="2.0" xmlns:ns1="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:ns2="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:Issuer>http://bfd.de</ns1:Issuer><ns1:Subject><ns1:NameID>Dieter Maurer</ns1:NameID></ns1:Subject><ns1:AuthnStatement AuthnInstant="2012-07-06T07:24:53.282142"><ns1:AuthnContext><ns1:AuthnContextClassRef>urn:oasis:names:tc:SAML2:2.0:ac:classes:Password</ns1:AuthnContextClassRef></ns1:AuthnContext></ns1:AuthnStatement><ns1:AttributeStatement><ns1:Attribute Name="Firstname"><ns1:AttributeValue xsi:type="ns2:string">Dieter</ns1:AttributeValue></ns1:Attribute><ns1:Attribute Name="Lastname"><ns1:AttributeValue xsi:type="ns2:string">Maurer</ns1:AttributeValue></ns1:Attribute></ns1:AttributeStatement></ns1:Assertion>
We define the signature context to support signing.
>>> from dm.saml2.signature import default_sign_context
>>> default_sign_context.add_key(xmlsec.Key.load('key.pem', xmlsec.KeyDataFormatPem, None), issuer.value())
We request that ``ass`` gets signed on serialization, serialize and
look at the result.
>>> ass.request_signature()
>>> signed = ass.toxml()
>>> print signed
<?xml version="1.0" ?><ns1:Assertion ID="_fb6dc6ac-9ee6-4a1f-8010-6dba6e0d9746" IssueInstant="2012-07-06T07:24:53.262859" Version="2.0" xmlns:ns1="urn:oasis:names:tc:SAML:2.0:assertion" xmlns:ns2="http://www.w3.org/2000/09/xmldsig#" xmlns:ns3="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><ns1:Issuer>http://bfd.de</ns1:Issuer><ns2:Signature><ns2:SignedInfo><ns2:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/><ns2:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"/><ns2:Reference URI="#_fb6dc6ac-9ee6-4a1f-8010-6dba6e0d9746"><ns2:Transforms><ns2:Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature"/><ns2:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"/></ns2:Transforms><ns2:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"/><ns2:DigestValue>6P0dLnMLJCe22YuRD1Mngiprz6k=</ns2:DigestValue></ns2:Reference></ns2:SignedInfo><ns2:SignatureValue>liaBBIVjk73x5spJrvfYg1Sa3VGnOqz0zqDKQr7qoLNg5/pzZ8llQEXQsbvw6zLh
26UnQ6D3KWvvabw9vpRqzLA21ykNUPqEGtZPMiQynvpdRSeTbg5ZyVBGYCL7ww19
MiEKryDwPI56I/3z4Le7KFZ4qpPPUptodQ4mm1PVsyA=</ns2:SignatureValue></ns2:Signature><ns1:Subject><ns1:NameID>Dieter Maurer</ns1:NameID></ns1:Subject><ns1:AuthnStatement AuthnInstant="2012-07-06T07:24:53.282142"><ns1:AuthnContext><ns1:AuthnContextClassRef>urn:oasis:names:tc:SAML2:2.0:ac:classes:Password</ns1:AuthnContextClassRef></ns1:AuthnContext></ns1:AuthnStatement><ns1:AttributeStatement><ns1:Attribute Name="Firstname"><ns1:AttributeValue xsi:type="ns3:string">Dieter</ns1:AttributeValue></ns1:Attribute><ns1:Attribute Name="Lastname"><ns1:AttributeValue xsi:type="ns3:string">Maurer</ns1:AttributeValue></ns1:Attribute></ns1:AttributeStatement></ns1:Assertion>
Now, we look how the verification can be done. We first set up
a verification context.
>>> from dm.saml2.signature import default_verify_context
>>> default_verify_context.add_key(xmlsec.Key.load('pubkey.pem', xmlsec.KeyDataFormatPem, None), issuer.value())
Calling ``CreateFromDocument`` will verify any (available) signatures and raise
an exception when a verification fails. Verification always uses
the ``Issuer`` to select the key from the verification context.
To check whether a signature
was verified at the instance, ``verified_signature`` can be called.
>>> verified_ass = CreateFromDocument(signed)
>>> verified_ass.verified_signature()
True
You can use ``pydoc``, the Python builtin ``help`` or look at the source
to find out more about this package.
Configuration
=============
Starting with version 3.1, the package provides an elementary way to
configure parts of the signature generation and verification process.
This may become necessary when SAML partner entities have special
requirements in this regard.
You do this kind of configuration by importing the module
``dm.saml2.config`` and overriding some of the variables defined there.
As an example, let us assume that one of your SAML2 partner entities
uses ``DsaSha1`` as the signature method (rather than the default
``RsaSha1``). Without special configuration, the verification will fail.
The ``xmlsec`` stack trace will give hints (somewhat cryptic) towards
a disabled transform. The configuration to get those SAML2 messages
verified could look like:
>>> from dm.saml2 import config
>>> from dm.xmlsec.binding import TransformDsaSha1
>>> config.signature_transforms += (TransformDsaSha1, )
This configuration tells the package that ``DsaSha1`` is an
acceptable signature method.
The configuration should happen once - before the first signature
creation/verification.
Notes
=====
Note that signature creation and verification will fail with an obscure
error message from ``xmlsec`` when ``xmlsec`` is not properly
initialized. Do not forget to call ``dm.xmlsec.binding.initialize()``.
History
=======
3.2.3
This version is identical to ``3.2.2`` with the exception
that it no longer declares its ``PyXB`` dependency in its ``setup.py``.
This allows the use of a (potentially differently named) ``PyXB``
replacement. Such a replacement becomes necessary for
``Python 3.10+`` because the latest ``PyXB`` release is no longer compatible.
For Python versions up to ``3.9`` use ``dm.saml2==3.2.2``.
3.2
Python 3 compatibity
Added test suite
Fixes in the `httpartifact` binding.
3.1.3
Added a 10 s timeout in ``metadata.EntityByUrl.get_metadata_document``.
It can be changed by changing the variable ``ENTITY_BY_URL_TIMEOUT``
in module ``metadata``.
3.1.2
Support (limited) type conversion in ``util.xs_convert_from_xml``.
3.1.1
Adapt to the changed binding for "plural" elements (``maxoccurs`` > 1)
in newer ``PyXB`` versions.
3.1
Elementary configuration support for the signature generation/verification
process.
Support for use of ``Sha256`` and ``RsaSha256`` as digest or
signature method, respcectively.
3.0
Switch to ``datetime`` values explicitely in the UTC time zone (rather
than naive ``datetime`` values which implicitely use the UTC time zone).
This also affects the lexical representation of SAML time values: they
now use the ``Z`` timezone suffix.
2.1
Signature support for the HTTP redirect binding.
Note: for this to work, you need at least version 1.3 of
``dm.xmlsec.binding`` which requires ``lxml >= 3.0``;
as Plone 4.x still uses ``lxml 2.x``, this version dependency
is not declared in ``setup.py``.
2.0
Version 2.0 uses ``dm.xmlsec.binding`` as Python binding to the XML
security library, rather then the no longer maintained ``pyxmlsec``.
This drastically facilitates installation.
1.0
Initial release based on ``pyxmlsec``.
Raw data
{
"_id": null,
"home_page": "http://pypi.python.org/pypi/dm.xmlsec.pyxb",
"name": "dm.saml2",
"maintainer": null,
"docs_url": null,
"requires_python": null,
"maintainer_email": null,
"keywords": "saml2 pyxb",
"author": "Dieter Maurer",
"author_email": "dieter@handshake.de",
"download_url": "https://files.pythonhosted.org/packages/5f/dd/2efc4320a25ebc2f6a14ba949fd11d79ab0f608b7d9e18a2c1a525160a7f/dm.saml2-3.2.3.tar.gz",
"platform": null,
"description": "This package provides support for SAML2 based on ``pyxb``.\n\n``pyxb`` (http://pypi.python.org/pypi/PyXB) generates a Python class\ncollection for an XML schema and provides means to convert between\nassociated Python instances and xml documents. It is used to generate\nand parse SAML2 messages.\n\nThe package adds support for digital signatures and SAML2 bindings and\nmetadata management.\n\n\nDependencies\n============\n\nPyXB\n----\n\nClass collections generated by ``pyxb`` tend to be very version dependent.\nThus, they must usually be regenerated when the ``pyxb`` version has changed.\n\nThe current package's version mostly uses class collections from\nthe ``wssplat`` and ``saml20`` bundles of ``pyxb``. Thus, they\nhave a good chance to be updated together with ``pyxb``.\nHowever, the ``pyxb`` ``saml2`` bundle lacks support for\nthe so called SAML2 context classes. This package contains\nclass collections generated with ``pyxb==1.1.4``. They need to\nbe regenerated if the ``pyxb`` version changes (and you use those classes --\nwhich is not very likely).\nThe ``gen.sh`` script in subpackage ``pyxb``\ncan provide clues how to regenerate them.\n\nThe original ``PyXB`` author (Peter A. Bigot) has\n`abandoned the project <https://github.com/pabigot/pyxb/blob/next/README.md>`_.\nThe latest release ``1.2.6`` is no longer compatible with modern\nPython versions (at least from ``Python 3.10`` on).\nTo handle this situation, ``dm.saml2`` no longer declares the ``PyXB``\ndependency in its ``setup.py``. This allows the use a ``PyXB`` replacement,\npotentially named differently.\nIf you want to use ``dm.saml2`` with Python 3.10+, you must provide\nsuch a replacement.\n\nI have not yet found a ``Python 3.10`` compatible replacement with\nthe required ``wssplat`` and ``saml20`` bundles.\nFor a customer project, I used the following approach:\nI started with the `PyXB-CTC 1.3.0 source distribution <https://pypi.org/project/pyxb-ctc/>`_, fixed there a few remaining ``Python 3.10`` incompatibilities (essentially replacing references to ``collections`` by corresponding ones to ``collections.abc``) and generated the missing ``wssplat`` and ``saml20`` bundles.\n\n\ndm.xmlsec.binding\n-----------------\n\nCheck its installation notes should you face related installation problems.\n\n\nExample\n=======\n\nThis section provides a simple example on how to create, sign and\nverify an assertion with this package.\n\n\nAlways ensure, the ``xmlsec`` library is initialized. Otherwise, it signing/\nsignature verification can fail with dubious messages.\n\n>>> import dm.xmlsec.binding as xmlsec\n>>> xmlsec.initialize()\n\nWe now build an assertion as Python object.\n\n>>> import pyxb.binding.datatypes as xs\n>>> from dm.saml2.pyxb.assertion import (NameID, Assertion, Subject, \\\n... AuthnStatement, AttributeStatement, AuthnContext, AuthnContextClassRef, \\\n... Attribute, AttributeValue, \\\n... CreateFromDocument\n... )\n>>> from datetime import datetime\n>>> \n>>> issuer = NameID('http://bfd.de')\n>>> ass = Assertion(issuer)\n>>> \n>>> subject = Subject(NameID('Dieter Maurer'))\n>>> \n>>> ass.Subject = subject\n>>> \n>>> authn = AuthnStatement(\n... None,\n... AuthnContext(AuthnContextClassRef('urn:oasis:names:tc:SAML2:2.0:ac:classes:Password')),\n... AuthnInstant=datetime.utcnow(),\n... )\n>>> \n>>> ass.AuthnStatement.append(authn)\n>>> \n>>> att = AttributeStatement(\n... # does not yet work perfectly -- needs further analysis\n... Attribute(xs.string('Dieter', _element=AttributeValue), Name='Firstname'),\n... Attribute(xs.string('Maurer', _element=AttributeValue), Name='Lastname'),\n... )\n>>> \n>>> ass.AttributeStatement.append(att)\n\nNow it looks like this (not yet signed).\n\n>>> unsigned_ass = ass.toxml()\n>>> print unsigned_ass\n<?xml version=\"1.0\" ?><ns1:Assertion ID=\"_fb6dc6ac-9ee6-4a1f-8010-6dba6e0d9746\" IssueInstant=\"2012-07-06T07:24:53.262859\" Version=\"2.0\" xmlns:ns1=\"urn:oasis:names:tc:SAML:2.0:assertion\" xmlns:ns2=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><ns1:Issuer>http://bfd.de</ns1:Issuer><ns1:Subject><ns1:NameID>Dieter Maurer</ns1:NameID></ns1:Subject><ns1:AuthnStatement AuthnInstant=\"2012-07-06T07:24:53.282142\"><ns1:AuthnContext><ns1:AuthnContextClassRef>urn:oasis:names:tc:SAML2:2.0:ac:classes:Password</ns1:AuthnContextClassRef></ns1:AuthnContext></ns1:AuthnStatement><ns1:AttributeStatement><ns1:Attribute Name=\"Firstname\"><ns1:AttributeValue xsi:type=\"ns2:string\">Dieter</ns1:AttributeValue></ns1:Attribute><ns1:Attribute Name=\"Lastname\"><ns1:AttributeValue xsi:type=\"ns2:string\">Maurer</ns1:AttributeValue></ns1:Attribute></ns1:AttributeStatement></ns1:Assertion>\n\n\nWe define the signature context to support signing.\n\n>>> from dm.saml2.signature import default_sign_context\n>>> default_sign_context.add_key(xmlsec.Key.load('key.pem', xmlsec.KeyDataFormatPem, None), issuer.value())\n\nWe request that ``ass`` gets signed on serialization, serialize and\nlook at the result.\n\n>>> ass.request_signature()\n>>> signed = ass.toxml()\n>>> print signed\n<?xml version=\"1.0\" ?><ns1:Assertion ID=\"_fb6dc6ac-9ee6-4a1f-8010-6dba6e0d9746\" IssueInstant=\"2012-07-06T07:24:53.262859\" Version=\"2.0\" xmlns:ns1=\"urn:oasis:names:tc:SAML:2.0:assertion\" xmlns:ns2=\"http://www.w3.org/2000/09/xmldsig#\" xmlns:ns3=\"http://www.w3.org/2001/XMLSchema\" xmlns:xsi=\"http://www.w3.org/2001/XMLSchema-instance\"><ns1:Issuer>http://bfd.de</ns1:Issuer><ns2:Signature><ns2:SignedInfo><ns2:CanonicalizationMethod Algorithm=\"http://www.w3.org/2001/10/xml-exc-c14n#\"/><ns2:SignatureMethod Algorithm=\"http://www.w3.org/2000/09/xmldsig#rsa-sha1\"/><ns2:Reference URI=\"#_fb6dc6ac-9ee6-4a1f-8010-6dba6e0d9746\"><ns2:Transforms><ns2:Transform Algorithm=\"http://www.w3.org/2000/09/xmldsig#enveloped-signature\"/><ns2:Transform Algorithm=\"http://www.w3.org/2001/10/xml-exc-c14n#\"/></ns2:Transforms><ns2:DigestMethod Algorithm=\"http://www.w3.org/2000/09/xmldsig#sha1\"/><ns2:DigestValue>6P0dLnMLJCe22YuRD1Mngiprz6k=</ns2:DigestValue></ns2:Reference></ns2:SignedInfo><ns2:SignatureValue>liaBBIVjk73x5spJrvfYg1Sa3VGnOqz0zqDKQr7qoLNg5/pzZ8llQEXQsbvw6zLh\n26UnQ6D3KWvvabw9vpRqzLA21ykNUPqEGtZPMiQynvpdRSeTbg5ZyVBGYCL7ww19\nMiEKryDwPI56I/3z4Le7KFZ4qpPPUptodQ4mm1PVsyA=</ns2:SignatureValue></ns2:Signature><ns1:Subject><ns1:NameID>Dieter Maurer</ns1:NameID></ns1:Subject><ns1:AuthnStatement AuthnInstant=\"2012-07-06T07:24:53.282142\"><ns1:AuthnContext><ns1:AuthnContextClassRef>urn:oasis:names:tc:SAML2:2.0:ac:classes:Password</ns1:AuthnContextClassRef></ns1:AuthnContext></ns1:AuthnStatement><ns1:AttributeStatement><ns1:Attribute Name=\"Firstname\"><ns1:AttributeValue xsi:type=\"ns3:string\">Dieter</ns1:AttributeValue></ns1:Attribute><ns1:Attribute Name=\"Lastname\"><ns1:AttributeValue xsi:type=\"ns3:string\">Maurer</ns1:AttributeValue></ns1:Attribute></ns1:AttributeStatement></ns1:Assertion>\n\nNow, we look how the verification can be done. We first set up\na verification context.\n\n>>> from dm.saml2.signature import default_verify_context\n>>> default_verify_context.add_key(xmlsec.Key.load('pubkey.pem', xmlsec.KeyDataFormatPem, None), issuer.value())\n\nCalling ``CreateFromDocument`` will verify any (available) signatures and raise\nan exception when a verification fails. Verification always uses\nthe ``Issuer`` to select the key from the verification context.\nTo check whether a signature\nwas verified at the instance, ``verified_signature`` can be called.\n\n>>> verified_ass = CreateFromDocument(signed)\n>>> verified_ass.verified_signature()\nTrue\n\n\nYou can use ``pydoc``, the Python builtin ``help`` or look at the source\nto find out more about this package.\n\n\nConfiguration\n=============\n\nStarting with version 3.1, the package provides an elementary way to\nconfigure parts of the signature generation and verification process.\nThis may become necessary when SAML partner entities have special\nrequirements in this regard.\n\nYou do this kind of configuration by importing the module\n``dm.saml2.config`` and overriding some of the variables defined there.\n\nAs an example, let us assume that one of your SAML2 partner entities\nuses ``DsaSha1`` as the signature method (rather than the default\n``RsaSha1``). Without special configuration, the verification will fail.\nThe ``xmlsec`` stack trace will give hints (somewhat cryptic) towards\na disabled transform. The configuration to get those SAML2 messages\nverified could look like:\n\n>>> from dm.saml2 import config\n>>> from dm.xmlsec.binding import TransformDsaSha1\n>>> config.signature_transforms += (TransformDsaSha1, )\n\nThis configuration tells the package that ``DsaSha1`` is an\nacceptable signature method.\n\nThe configuration should happen once - before the first signature\ncreation/verification.\n\n\nNotes\n=====\n\nNote that signature creation and verification will fail with an obscure\nerror message from ``xmlsec`` when ``xmlsec`` is not properly\ninitialized. Do not forget to call ``dm.xmlsec.binding.initialize()``.\n\n\nHistory\n=======\n\n3.2.3\n\n This version is identical to ``3.2.2`` with the exception\n that it no longer declares its ``PyXB`` dependency in its ``setup.py``.\n This allows the use of a (potentially differently named) ``PyXB``\n replacement. Such a replacement becomes necessary for\n ``Python 3.10+`` because the latest ``PyXB`` release is no longer compatible.\n For Python versions up to ``3.9`` use ``dm.saml2==3.2.2``.\n\n3.2\n\n Python 3 compatibity\n\n Added test suite\n\n Fixes in the `httpartifact` binding.\n\n3.1.3\n\n Added a 10 s timeout in ``metadata.EntityByUrl.get_metadata_document``.\n It can be changed by changing the variable ``ENTITY_BY_URL_TIMEOUT``\n in module ``metadata``.\n\n3.1.2\n\n Support (limited) type conversion in ``util.xs_convert_from_xml``.\n\n3.1.1\n\n Adapt to the changed binding for \"plural\" elements (``maxoccurs`` > 1)\n in newer ``PyXB`` versions.\n\n3.1\n\n Elementary configuration support for the signature generation/verification\n process.\n\n Support for use of ``Sha256`` and ``RsaSha256`` as digest or\n signature method, respcectively.\n\n\n3.0\n\n Switch to ``datetime`` values explicitely in the UTC time zone (rather\n than naive ``datetime`` values which implicitely use the UTC time zone).\n\n This also affects the lexical representation of SAML time values: they\n now use the ``Z`` timezone suffix.\n\n2.1\n\n Signature support for the HTTP redirect binding.\n Note: for this to work, you need at least version 1.3 of\n ``dm.xmlsec.binding`` which requires ``lxml >= 3.0``;\n as Plone 4.x still uses ``lxml 2.x``, this version dependency\n is not declared in ``setup.py``. \n\n2.0\n\n Version 2.0 uses ``dm.xmlsec.binding`` as Python binding to the XML\n security library, rather then the no longer maintained ``pyxmlsec``.\n This drastically facilitates installation.\n\n1.0\n\n Initial release based on ``pyxmlsec``.",
"bugtrack_url": null,
"license": "BSD",
"summary": "SAML2 support based on PyXB",
"version": "3.2.3",
"project_urls": {
"Homepage": "http://pypi.python.org/pypi/dm.xmlsec.pyxb"
},
"split_keywords": [
"saml2",
"pyxb"
],
"urls": [
{
"comment_text": "",
"digests": {
"blake2b_256": "5fdd2efc4320a25ebc2f6a14ba949fd11d79ab0f608b7d9e18a2c1a525160a7f",
"md5": "85112cd8780cefcc9d82082dac6ec66a",
"sha256": "7f933f33ec77992ce24f30cc2ede33a0a14bad646eaf10386a8302fe800ef680"
},
"downloads": -1,
"filename": "dm.saml2-3.2.3.tar.gz",
"has_sig": false,
"md5_digest": "85112cd8780cefcc9d82082dac6ec66a",
"packagetype": "sdist",
"python_version": "source",
"requires_python": null,
"size": 345212,
"upload_time": "2024-01-30T08:51:23",
"upload_time_iso_8601": "2024-01-30T08:51:23.365295Z",
"url": "https://files.pythonhosted.org/packages/5f/dd/2efc4320a25ebc2f6a14ba949fd11d79ab0f608b7d9e18a2c1a525160a7f/dm.saml2-3.2.3.tar.gz",
"yanked": false,
"yanked_reason": null
}
],
"upload_time": "2024-01-30 08:51:23",
"github": false,
"gitlab": false,
"bitbucket": false,
"codeberg": false,
"lcname": "dm.saml2"
}
JSON