yahoo-eng-team team mailing list archive

[Dolph Mathews <1298478@xxxxxxxxxxxxxxxxxx>]

Valuable changes were made as part of that blueprint, but as documented
in the attached code reviews, we stopped short of actually allowing role
assignments to non-existent users due to a lack of use cases that were
not already solved (by group role assignments, for example). If you have
a use case for this behavior that is more important than the poor user
experience that would result from erroneous role assignments, please
share it and we'll be happy to reconsider and look for a compromise.

** Changed in: keystone
       Status: New => Invalid

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

Title:
  Can't add roles to non-existing users

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  The following blueprint is said to be implemented but it isn't:
  https://blueprints.launchpad.net/keystone/+spec/no-check-id

  If you try to add roles to a user that doesn't exist you get a 404:
  {
      "error": {
          "code": 404,
          "message": "Could not find user, 123456.",
          "title": "Not Found"
      }
  }

  The tests that are implemented for this feature expect to get a 404
  also (see the tests here:
  https://review.openstack.org/#/c/72098/5/keystone/tests/test_v3_identity.py):

  self.put(member_url, expected_status=404)

  So, the blueprint has not been implemented as intended.

  Thanks,
  Udi.

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