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

NameError: uninitialized constant Net::LDAP::AuthAdapter::Sasl::MaxSaslChallenges #73

Open
vlymar opened this issue Feb 13, 2017 · 2 comments

Comments

@vlymar
Copy link

vlymar commented Feb 13, 2017

There's a bug in the current version of net-ldap that causes this exception if you're trying to use SASL authentication. The fix was just merged (ruby-ldap/ruby-net-ldap#281), but the maintainers are waiting to merge a few more PRs before releasing a new version.

I'm opening this issue for anyone else who might stumble across this error.

To the maintainer(s) of omniauth-ldap, once net-ldap gets a version bump, can we point the gemspec at the new version?

@vlymar
Copy link
Author

vlymar commented Mar 6, 2017

Update

ruby-ldap was just recently bumped to version 0.16.0. This bump fixes the SASL bug mentioned in this issue. Changelog: https://github.com/ruby-ldap/ruby-net-ldap/blob/master/History.rdoc

This version also enables hostname verification, which allows you to pass an option to ruby-ldap to force it to check if the LDAP server's hostname actually matches the name on the SSL certificate returned (it doesn't do this by default). See also: #58

Is there any chance of bumping to 0.16.0? Until then, as far as I can tell omniauth-ldap does not support SASL auth.

@stakach
Copy link

stakach commented Oct 24, 2017

Also uninitialized constant OmniAuth::Strategies::SAML::ValidationError

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

2 participants