← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1329554] [NEW] Setting token hashing to greater than sha256 will not work with the SQL token backend

 

Public bug reported:

The SQL Token backend sets the ID of the token to a 64 column. sha512
will generate a 128 character (byte) string.

>>> a =hashlib.sha512('test').hexdigest()
>>> a
'ee26b0dd4af7e749aa1a8ee3c10ae9923f618980772e473f8819a5d4940e0db27ac185f8a0e1d5f84f88bc887fd67b143732c304cc5fa9ad8e6f57f50028a8ff'
>>> len(a)
128
>>>

** Affects: keystone
     Importance: Medium
         Status: New

** Changed in: keystone
   Importance: Undecided => Medium

** Summary changed:

- Setting token hashing to sha512 will not work with the SQL token backend
+ Setting token hashing to greater than sha256 will not work with the SQL token backend

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1329554

Title:
  Setting token hashing to greater than sha256 will not work with the
  SQL token backend

Status in OpenStack Identity (Keystone):
  New

Bug description:
  The SQL Token backend sets the ID of the token to a 64 column. sha512
  will generate a 128 character (byte) string.

  >>> a =hashlib.sha512('test').hexdigest()
  >>> a
  'ee26b0dd4af7e749aa1a8ee3c10ae9923f618980772e473f8819a5d4940e0db27ac185f8a0e1d5f84f88bc887fd67b143732c304cc5fa9ad8e6f57f50028a8ff'
  >>> len(a)
  128
  >>>

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1329554/+subscriptions


Follow ups

References