auth_token middleware hashes tokens with configurable algorithm
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
openstack-manuals |
Fix Released
|
Undecided
|
Gauvain Pocentek |
Bug Description
https:/
Dear documentation bug triager. This bug was created here because we did not know how to map the project name "openstack/
commit 22db04bb6bee3ab
Author: Brant Knudson <email address hidden>
Date: Tue May 6 19:36:59 2014 -0500
auth_token middleware hashes tokens with configurable algorithm
The auth_token middleware always hashed PKI Tokens with MD5. This
change makes it so that PKI tokens can be hashed with SHA256 or any
other algorithm supported by hashlib.new(). This is for security
hardening.
auth_token has a new config option 'hash_algorithms' that is set
to the list of algorithms that will be used for hashing PKI tokens.
This will typically be set to a single hash algorithm which must
match the hash algorithm set in Keystone. Otherwise the tokens
in the revocation list will not match, leading to revoked tokens
being still usable.
During a transition from one algorithm to another,
'hash_
algorithm. Both of the hash algorithms will be used to match
against the revocation list and cache. Once the tokens using the
old algorithm have expired the old algorithm can be removed from
the list.
'hash_
DocImpact
SecurityImpact
Closes-Bug: #1174499
Change-Id: Ie524125dc5f6f1
This will need to be reflected in the config-ref for all the projects, since they all use keystone_authtoken.
The security guide might be impacted by this too?