-
Notifications
You must be signed in to change notification settings - Fork 421
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
xmlsec can not read already opened file (djangosaml2) #944
Comments
this issue should be moved to pysaml2 the issue is related to windows's kernel that have tese kind of problem in accessing files in parallel R/W ops |
The issue is already in pysaml2, isn't it? Maybe you sugest moving the issue to djangosaml2? |
Did you manage to find a fix for this? I'm having the same issue. |
No, sorry. It seems thats an OS "feature". |
Hello:
I am facing some issues while trying to make the djangosaml2 sample work in Windows. I can not sign the request before sending it to the IdP because xmlsec can not read the temporary file with the assertion XML. The problem is that this temporary file keeps opened by python process and the xmlsec process can not open it.
Code Version
pysaml2 7.4.2
djangosaml2 1.8.0
Expected Behavior
The _run_xmlsec method signs the temporary file XML.
Current Behavior
I think the problem is in sigver.py sign_statement function:
The make_temp function does not close the tempfile after creating it, so the xmlsec.exe process can not open it.
I managed to copy the assertion XML to other file and I was able to sign it:
Possible Solution
No idea.
Steps to Reproduce
Just clone the djangosaml2 project, configure it and try to login.
The text was updated successfully, but these errors were encountered: