The revocation event test used "user_domain_id" and
"project_domain_id" as token fields that the "domain_id"
revocation event field maps to, but the token fields are
actually "identity_domain_id" and "assignment_domain_id", as
can be seen in
keystone.contrib.revoke.model.build_token_values().
Conflicts:
keystone/tests/test_revoke.py
Change-Id: I208484da243403287eaa33893d57429c7e6d27c7
Partial-Bug: #1349597
(cherry picked from commit c4447f16da036fe878382ce4e1b05b84bdcc4d4e)
Reviewed: https:/ /review. openstack. org/112083 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=cccc3f3239c 68479de0f6a41bd 64badf2a9ec9e7
Committed: https:/
Submitter: Jenkins
Branch: stable/icehouse
commit cccc3f3239c6847 9de0f6a41bd64ba df2a9ec9e7
Author: Brant Knudson <email address hidden>
Date: Sat Jul 26 11:21:45 2014 -0500
Correct revocation event test for domain_id
The revocation event test used "user_domain_id" and domain_ id" as token fields that the "domain_id" domain_ id" and "assignment_ domain_ id", as contrib. revoke. model.build_ token_values( ).
"project_
revocation event field maps to, but the token fields are
actually "identity_
can be seen in
keystone.
Conflicts:
keystone/ tests/test_ revoke. py
Change-Id: I208484da243403 287eaa33893d574 29c7e6d27c7 878382ce4e1b05b 84bdcc4d4e)
Partial-Bug: #1349597
(cherry picked from commit c4447f16da036fe