Callback stuck on auth.process_response

[NeuraByte-UCSD-ITS]

backend: Fast API frontEnd: Next.js python3-saml version 1.15.0

Hi, I am using python3-saml for SSO implementation in my project which successfully takes me to the login page, Once I enter my credentials press login button it triggers callback function which gets stuck on this line "auth.process_response"

[jshelley]

I am having this same issue.

[pitbulk]

Can you add a debugger and see where inside the process_response got stuck?

[NeuraByte-UCSD-ITS]

Hi, I was able to get that issue resolved by downgrading the lbxml library from version lxml==5.1.0 to lxml==4.9.4. However, now I have another issue. When I try to get attributes I am unable to get email, can this be configured in settings.json, advanced_settings.jscon or in saml.py?

---

[pitbulk]

I was able to get that issue resolved by downgrading the lbxml library from version lxml==5.1.0 to lxml==4.9.4

Have you tried to install the lxml library as follows:

pip install --force-reinstall --no-binary lxml lxml

When I try to get attributes I am unable to get email

It seems the IdP is providing username, eduPersonScopedAffiliation, firstname, lastname, fullname but not the email. You will need to contant the IdP administrator and ask them to release the email info in the SAMLResponse.

[lovelydett]

lxml==4.9.3 works, thx for saving my day.

[smaccona]

I had this issue with a Django 4.2 app. I can confirm that installing lxml via pip install --force-reinstall --no-binary lxml lxml seems to have fixed it. @pitbulk do you have any insight into why the binary package for lxml doesn't work? We prefer to use binaries in our build pipeline when possible.

I can also confirm that downgrading to lxml==4.9.4 also worked for us. That's what we're using in our build at the moment.

[pitbulk]

@smaccona if you search in the Issues section there were tons of issues recently with the lxml version for different reasons.

The main issue was due to incompatibilities with libxml2.

@NeuraByte-UCSD-ITS , you should not be using async calls for the SAML handshake.