Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Callback stuck on auth.process_response #396

Open
NeuraByte-UCSD-ITS opened this issue Feb 14, 2024 · 6 comments
Open

Callback stuck on auth.process_response #396

NeuraByte-UCSD-ITS opened this issue Feb 14, 2024 · 6 comments

Comments

@NeuraByte-UCSD-ITS
Copy link

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"

image image image image
@jshelley
Copy link

I am having this same issue.

@pitbulk
Copy link
Contributor

pitbulk commented Feb 19, 2024

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

@NeuraByte-UCSD-ITS
Copy link
Author

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?

image --- image

@pitbulk
Copy link
Contributor

pitbulk commented Feb 20, 2024

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
Copy link

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

@smaccona
Copy link

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants