-
-
Notifications
You must be signed in to change notification settings - Fork 881
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
Add xmlsec with no-binary option #1230
Conversation
SAML backend is still not working. I have the issue "lxml & xmlsec libxml2 library version mismatch".
@cimnine Should this fix be automatically updated into new docker hub builds? I'm still experiencing these issues on version v4.0.5-2.9.1 (updated 2 days ago). |
It will be when we release a new version of the NB Docker project. (That's the 2.9.1 part of the tag) |
If you need the correction, you could temporary use my image, docker pull ghcr.io/lchastel/netbox-docker:snapshot-2.9.1 @cimnine : Could you please check the Github Actions workflow ? (cf #1258) |
Thank you! I'll use it until the next version has been published. |
SAML backend is still not working.
I have the issue "lxml & xmlsec libxml2 library version mismatch".
Related Issue:
New Behavior
Adding xmlsec to requirements-container.txt for python3-saml like it's done for lxml solve the issue.
Contrast to Current Behavior
When enabling SAML backend, I receives the error message
lxml & xmlsec libxml2 library version mismatch
How to reproduce ?
Follow Quickstart of netbox-docker
Add next lines to env/netbox.env
REMOTE_AUTH_BACKEND='social_core.backends.saml.SAMLAuth'
DEBUG=true
Start or restart netbox
docker compose up -d
Connect to the netbox instance (you may have to click on login)
Here is the result ...
Discussion: Benefits and Drawbacks
...
Changes to the Wiki
...
Proposed Release Note Entry
...
Double Check
develop
branch.