yahoo-eng-team team mailing list archive

Thread
Date

[Bug 1901654] [NEW] generate_public_ID() should handle bytes data type because local_id may be assigned in bytes data type.

To: yahoo-eng-team@xxxxxxxxxxxxxxxxxxx
From: Keigo Noha <1901654@xxxxxxxxxxxxxxxxxx>
Date: Tue, 27 Oct 2020 05:20:15 -0000
Reply-to: Bug 1901654 <1901654@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Public bug reported:

Currently generate_public_ID() in keystone/identity/id_generators/sha256.py assumes that mapping parameter contains str data type only.
However, python-ldap library will return bytes data type if it is retrieved from attributes.

That is described at https://www.python-ldap.org/en/python-
ldap-3.3.0/bytes_mode.html.

That means local_id or else may contain any type of data, which will be
represented as bytes data type.

** Affects: keystone
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Identity (keystone).
https://bugs.launchpad.net/bugs/1901654

Title:
  generate_public_ID() should handle bytes data type because local_id
  may be assigned in bytes data type.

Status in OpenStack Identity (keystone):
  New

Bug description:
  Currently generate_public_ID() in keystone/identity/id_generators/sha256.py assumes that mapping parameter contains str data type only.
  However, python-ldap library will return bytes data type if it is retrieved from attributes.

  That is described at https://www.python-ldap.org/en/python-
  ldap-3.3.0/bytes_mode.html.

  That means local_id or else may contain any type of data, which will
  be represented as bytes data type.

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