I've tested v3.0 with the SAML2CustomAttrUserBackend and everything seems to be working.
I've updated the README to include 3.0 and have clarified REMOTE_AUTH_BACKEND since it seems to be
a common configuration error.
One thing to note is that a version of pysaml2 that includes IdentityPython/pysaml2@1b9723753fae3fc535b0e18e236d2d87f3cc2353 must be used for Python 3.9+ support. Perhaps you could push another version of django3-auth-saml2 with updated requirements to pypi? I've tested the plugin with pysaml2 v6.5.2 and everything seems to work fine.
@devon-mar - thank you very much for taking the time to validate the plugin with v3.0 and providing a PR for the readme. I really appreciate your efforts.
I've tested v3.0 with the
SAML2CustomAttrUserBackend
and everything seems to be working. I've updated the README to include 3.0 and have clarifiedREMOTE_AUTH_BACKEND
since it seems to be a common configuration error.One thing to note is that a version of pysaml2 that includes IdentityPython/pysaml2@1b9723753fae3fc535b0e18e236d2d87f3cc2353 must be used for Python 3.9+ support. Perhaps you could push another version of django3-auth-saml2 with updated requirements to pypi? I've tested the plugin with pysaml2 v6.5.2 and everything seems to work fine.