Without this patch, when an OAuth1 request token is authorized with a
limited set of roles, the roles for the access token are ignored when
the user uses it to request a keystone token. This means that user of an
access token can use it to escallate their role assignments beyond what
was authorized by the creator. This patch fixes the issue by ensuring
the token model accounts for an OAuth1-scoped token and correctly
populating the roles for it.
Change-Id: I02f9836fbd4d7e629653977fc341476cfd89859e
Closes-bug: #1873290
(cherry picked from commit 6c73690f779a42a5c62914b6bc37f0ac2f41a3e3)
Reviewed: https:/ /review. opendev. org/725887 /git.openstack. org/cgit/ openstack/ keystone/ commit/ ?id=ba89d27793c 2d3a26ad9564266 0fa9bd820ed3be
Committed: https:/
Submitter: Zuul
Branch: stable/ussuri
commit ba89d27793c2d3a 26ad95642660fa9 bd820ed3be
Author: Colleen Murphy <email address hidden>
Date: Thu Apr 16 20:35:46 2020 -0700
Ensure OAuth1 authorized roles are respected
Without this patch, when an OAuth1 request token is authorized with a
limited set of roles, the roles for the access token are ignored when
the user uses it to request a keystone token. This means that user of an
access token can use it to escallate their role assignments beyond what
was authorized by the creator. This patch fixes the issue by ensuring
the token model accounts for an OAuth1-scoped token and correctly
populating the roles for it.
Change-Id: I02f9836fbd4d7e 629653977fc3414 76cfd89859e 5c62914b6bc37f0 ac2f41a3e3)
Closes-bug: #1873290
(cherry picked from commit 6c73690f779a42a