django-saml2-auth
django-saml2-auth copied to clipboard
fangli
How to handle Certificates and Signature Errors?
My concern is how we can handle these kind of errors while implementing Azure Active Directory as Identity Provider.
I have this error as well; I have a sneaking suspicion it's not actually to do with the certificate but I'm not sure how else to troubleshoot this to move forward.
Any tips appreciated.
Receiving the same issue on Windows Server. Please add some detailed documentation or resolution.
Depending on the operational system you will also need to install additional libraries. I had the same issue and found out that the configuration was correct, but there were some missing libraries and xmlsec wasn't working as expected.
In my case, I got the issue on a CentOS server, so I needed to install more 2 dependencies in addition to xmlsec1:
yum install libffi-devel xmlsec1 xmlsec1-openssl
This solved my problem. You should also have a look on Okta's documentation. They have a guide on how to use PySAML2 to add support for Okta (via SAML) to applications written in Python.
https://developer.okta.com/code/python/pysaml2/
I'm seeing this same issue with a project running on Windows Server 2016 and IIS, using ADFS as my identity provider.
I am curious to know if anyone running on Windows Server has found a resolution to it.
Depending on the operational system you will also need to install additional libraries. I had the same issue and found out that the configuration was correct, but there were some missing libraries and xmlsec wasn't working as expected.
In my case, I got the issue on a CentOS server, so I needed to install more 2 dependencies in addition to xmlsec1:
yum install libffi-devel xmlsec1 xmlsec1-openssl
This solved my problem. You should also have a look on Okta's documentation. They have a guide on how to use PySAML2 to add support for Okta (via SAML) to applications written in Python.
https://developer.okta.com/code/python/pysaml2/
Actually xmlsec and xmlsec1 is not available natively for windows neither the openssl library. We have to build them according to the need which is a hactic solution for the ones who are doing it for the first time. Since I haven't received any resolution from the developers here, so I have shifted to a small Redhat VM to accomplish the task. If any django_saml2_auth developer is reading this, we need a resolution to apply it on windows. And also some detailed information on the issues and how to resolve them.
