yahoo-eng-team team mailing list archive

[Kirill Zaborsky <qrilka@xxxxxxxxx>]

Public bug reported:

It looks like Keystone uses some a bit strange conception of Base64 which does not include slashes - https://github.com/openstack/keystone/commit/bcc0f6d6fc1f674bc4b340d041b28bc1cfddf66a
http://tools.ietf.org/html/rfc4648 shows that slash is a valid Base64 character.

So currently for some unknown reason Keystone replaces slashes with
dashes when returning tokens and does the opposite when reading tokens.

I understand that fixing this will break backwards compatibility but it
makes sense at least to document this strange behaviour so developers
accessing Keystone not with Keystone original bindings (e.g. from othe
languages) will not be caught by surprise.

** Affects: keystone
     Importance: Undecided
         Status: New

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

Title:
  Meaningless replacing of slashes with dashes in Keystone tokens

Status in OpenStack Identity (Keystone):
  New

Bug description:
  It looks like Keystone uses some a bit strange conception of Base64 which does not include slashes - https://github.com/openstack/keystone/commit/bcc0f6d6fc1f674bc4b340d041b28bc1cfddf66a
  http://tools.ietf.org/html/rfc4648 shows that slash is a valid Base64 character.

  So currently for some unknown reason Keystone replaces slashes with
  dashes when returning tokens and does the opposite when reading
  tokens.

  I understand that fixing this will break backwards compatibility but
  it makes sense at least to document this strange behaviour so
  developers accessing Keystone not with Keystone original bindings
  (e.g. from othe languages) will not be caught by surprise.

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