Implicitly ignore attributes that are mapped to None in LDAP

Attributes that are mapped to None in LDAP trigger a 500 error when
performing a search if they are not explicitly ignored in keystone's
configuration.  These attributes should always be ignored, even if
the admin left the attribute out of the ignore list.

Change-Id: Ibbabdd0013059d5720250816764021a0b3ce8ce0
Closes-bug: #1335437
Regenerate sample config file

The sample config file was regenerated using:
  tox -r -e sample_config

Change-Id: Idc5341b343c4fa5150be47c9c01cd67e216b1142
Fixed tox cover environment to share venv

Change-Id: I57c6dc53c3ebda7bf7530f7805decafe93d474f3
Adds coverage report to py33 test runs

Change-Id: I976482d92f0036c01da65640207db441b4500860
Initial implementation of validator

This is the initial implementation of a jsonschema type
validator for the Keystone API. Something very similar to this is used
in Nova V3 for validation. By using jsonschema to validate API requests,
we can make parameters that are passed in fit the criteria we allow and
what is specified in the Identify API spec. This will also allow us to
validate parameters by wrapping the method that needs validation.

bp: api-validation
Change-Id: I1e1dc8e5ac3ad766f05444b16d56a22c89602b9f
Merge "Implicitly ignore attributes that are mapped to None in LDAP"
Merge "Regenerate sample config file"
Merge "Fixed tox cover environment to share venv"
Merge "Adds coverage report to py33 test runs"