Previously, the assertValidProjectScopedTokenResponse 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.
Reviewed: https:/ /review. openstack. org/253670 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=fe14d330c7a 5528a7a78c04455 67845d62d3b2c0
Committed: https:/
Submitter: Jenkins
Branch: master
commit fe14d330c7a5528 a7a78c044556784 5d62d3b2c0
Author: Lance Bragstad <email address hidden>
Date: Mon Dec 7 22:41:57 2015 +0000
Add checks for project scoped data creep to tests
Previously, the assertValidProj ectScopedTokenR esponse 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.
Change-Id: I4ebb86af973ed6 af001373756a69a f9586bdefcf
Closes-Bug: 1224273