fix(saml): extracting key data points issue #3570

[brianray]

Submitting Pull Requests

General

• Make sure you use semantic commit messages.
  Examples: "fix(google): Fixed foobar bug", "feat(accounts): Added foobar feature".
• All Python code must formatted using Black, and clean from pep8 and isort issues.
• JavaScript code should adhere to StandardJS.
• If your changes are significant, please update ChangeLog.rst.
• If your change is substantial, feel free to add yourself to AUTHORS.

Provider Specifics

In case you add a new provider:

• Make sure unit tests are available.
• Add an entry of your provider in test_settings.py::INSTALLED_APPS and docs/installation.rst::INSTALLED_APPS.
• Add documentation to docs/providers/<provider name>.rst and docs/providers/index.rst Provider Specifics toctree.
• Add an entry to the list of supported providers over at docs/overview.rst.

[pennersr]

We really need to extend the test suite for this case. Can you look into that, or, send me one of your SAML payloads so that I can introspect/extend it myself?

[coveralls]

coverage: 95.859% (-0.005%) from 95.864%
when pulling f928ceb on brianray:main
into 32c9eaf on pennersr:main.

[pennersr]

Fixed via 6251d5e