We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Hi,
since updating to revision 1.6.1 you will need to use
require 'active_directory'
regardless if you run this from bundle exec
otherwise when you run
ActiveDirectory::Base.setup(settings)
you will get
uninitialized constant ActiveDirectory::Base
this breaks behavior from 1.6.0
The text was updated successfully, but these errors were encountered:
Sorry for the inconvenience. As the gem as no bin, could you tell me what you are trying to exec ?
Sorry, something went wrong.
ok add the gem to you Gemfile require 'active_directory'
add a config or initializer that has the setting for the ActiveDirectory::Base.setup(settings)
bundle exec rails c
ActiveDirectory::User.find(:first, :userprincipalname => "[email protected]")
The way around this would be to use require 'active_directory' in side the config or initializer
Thats the problem. 1.6.0 didnt need this. If the gem was in the gem file then it automatically required.
No branches or pull requests
Hi,
since updating to revision 1.6.1 you will need to use
regardless if you run this from bundle exec
otherwise when you run
you will get
uninitialized constant ActiveDirectory::Base
this breaks behavior from 1.6.0
The text was updated successfully, but these errors were encountered: