Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Considering we are bumping net-ldap from 0.3.1 to 0.7.0 I thought a
minor version bump might be called for.

net-ldap version update

There is a bug in net-ldap < 0.5.0 preventing connections to Microsoft servers. Pushing the net-ldap dependency version should fix it. See the following net-ldap issue for a description.

https://github.com/ruby-ldap/ruby-net-ldap/issues/80

See merge request !2

https://github.com/ruby-ldap/ruby-net-ldap/issues/80

Sync with intridea/omniauth-ldap

Update version to match intridea/omniauth-ldap.
Add test for alternate fields.

Conflicts:
	README.md
	spec/omniauth/strategies/ldap_spec.rb

Minor documentation fix

Update net-ldap gem to avoid errors with some LDAP Servers

gitignore Gemfile.lock

add license information to the gemspec

Conflicts:
	spec/omniauth/strategies/ldap_spec.rb

Gemfile.lock: update net-ldap to fix LDAP authentication issues

Newer LDAP servers fail with older versions of net-ldap.
Update to the fixed version.

Signed-off-by: David Aguilar <davvid@gmail.com>

The Gemfile.lock shouldn't be included in a gem-based repository
because it may artificially lock obsolete gems.

An example of this is rb-fsevent which at the version it was
locked at is incompatable with OS X 10.8

If something does need the version locked, specify it in the
.gemspec or Gemfile itself.

This way it can be used with rubygems.org API

Reformatted specs and reworked way to propagate InvalidCredentials error to application

AD allows bind with with correct username and empty password
so application will think user successfully authenticated which
is a serious mistake

When exception is raised from middleware host application can not
handle it. This is why OmniAuth uses #failure! which sends message to
application so it can do something about it

Report missing credentials to the Rails application.

If no username or password is provided a MissingCredentialsError is
raised which causes a Rack caught exception and a 500 Error in gitlab.
Omniauth provides a way to raise such errors to the application by
using the 'fail!' method to pass the exception to the registered
failure handler. For gitlab this is the omniauth_controller code.

This is required to resolve gitlab issue #1077.

Signed-off-by: Pat Thoyts <patthoyts@users.sourceforge.net>