b626a3ca86
This patch moves (as discussed at the Newton design summit) the s3_token middleware from keystonemiddleware to swift3. The git history is not included based upon the agreement between the Keystone team and the Swift3 team. This is based on s3_token.py from openstack/keystonemiddleware@234913e Note that the egg entrypoint has changed from "s3_token" to "s3token" for consistency between entrypoint and recommended pipeline names. Additionally, keystone functional tests now use the in-tree s3token middleware. Upgrade Impact ============== Deployers currently using keystone for authentication should change their s3token filter definition to use the middleware provided by swift3 rather than the one provided by keystonemiddleware. Note that keystonemiddleware will still need to be installed, and its auth_token middleware configured. UpgradeImpact Co-Authored-By: Tim Burke <tim.burke@gmail.com> Co-Authored-By: Kota Tsuyuzaki <tsuyuzaki.kota@lab.ntt.co.jp> Change-Id: I1c0e68a5276dd3dee97d7569e477c784db8ccb8a
5 lines
66 B
Plaintext
5 lines
66 B
Plaintext
swift>=2.1.0
|
|
lxml
|
|
requests!=2.9.0,>=2.8.1 # Apache-2.0
|
|
six>=1.9.0
|