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.

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

the request phase, since the adaptor now is only instantiated on
the callback phase.

Move Adaptor instance initializtion in callback phase

Move Adaptor instance initializtion in callback phase, which can make setup phase work correctly. And also do some indentation fix.

Use :raw_info instead of 'original_ldap_entry'

Remove beta notice

Net::LDAP::Entry always returns an array of values.  

Net::LDAP::Entry (http://net-ldap.rubyforge.org/Net/LDAP/Entry.html) explicitly
returns an array of values for each attribute. The result of OmniAuth::Strategies::LDAP#map_user
was returning a string representation of the attribute values array (ie. "['attribute_value']"),
and it should be returning the actual attribute value.

Remove ruby-debug dependency

Wrapping original LDAP info in a hash so it doesn't break omniauth auth_hash interface

Conflicts:
	omniauth-ldap.gemspec

bump the version to 1.0.0

spec. Added spec test for ldap strategy