mapping engine ignores multiple assertion values when using regex

[Steve Martinelli]

Previously, if the mapping engine saw a regex value, it would only compare the first "mapping value" and the first "assertion value".

For instance, if the mapping value was from the ".*tester*" and the assertion values were ['developer','tester','deployer'] it will fail the mapping check.

The solution would be to actually iterate over the assertion values until no match is found.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/94518

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/94518
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=713ddcf0b38a4460368a8c523260b4a48bd98ce9
Submitter: Jenkins
Branch: master

commit 713ddcf0b38a4460368a8c523260b4a48bd98ce9
Author: Steve Martinelli <email address hidden>
Date: Tue May 20 22:58:29 2014 -0400

    Mapping engine does not handle regex properly

    Currently, if there is more than one assertion value (the list of
    group ids returned from the idp). Then when using regex to compare
    again the mapping values, only the first values are used.

    Change-Id: Iba7d455ef0d5fc2d4ac16f4a7eb553845270fb2c
    Closes-Bug: #1321536