Previously, the assertValidUnscopedTokenResponse method only
ensured specific attributes were in the token response. These
checks didn't ensure that the token scope never grew.
This change makes it so that the assertion will fail if extra
attributes are added to the token response. This should help
us be more aware of changes that have token response data
creep by building the check into the tests.
This is implemented using the existing jsonschema work that
keystone has for validating API requests.
Reviewed: https:/ /review. openstack. org/254258 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=1ad62ef692b 43b28fb96b79a36 98bd2a5be85015
Committed: https:/
Submitter: Jenkins
Branch: master
commit 1ad62ef692b43b2 8fb96b79a3698bd 2a5be85015
Author: Lance Bragstad <email address hidden>
Date: Mon Dec 7 15:38:00 2015 +0000
Add checks for token data creep using jsonschema
Previously, the assertValidUnsc opedTokenRespon se method only
ensured specific attributes were in the token response. These
checks didn't ensure that the token scope never grew.
This change makes it so that the assertion will fail if extra
attributes are added to the token response. This should help
us be more aware of changes that have token response data
creep by building the check into the tests.
This is implemented using the existing jsonschema work that
keystone has for validating API requests.
Change-Id: I15acd58a9efaac 65ba066fbb7b81f 15797b6573c
Partial-Bug: 1224273