yahoo-eng-team team mailing list archive

[Morgan Fainberg <morgan.fainberg@xxxxxxxxx>]

V2 will not be changed at this point the API and how it handles
authorization for actions is frozen. Development focus is on V3. We have
active bugs/tasks to make the V3 cloud policy the default.

I am closing this bug as "won't fix" as we aren't going to change V2 API
in a meaningful way unless it is to address a critical security issue.

** Changed in: keystone
       Status: New => Won't Fix

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

Title:
  Add simultaneous v2 and v3 API policy support

Status in OpenStack Identity (Keystone):
  Won't Fix

Bug description:
  Default policy.json file in Keystone is focused on v2 API nowadays.
  From the (Tempest) testing point-of-view we need to test both
  supported API's simultaneously, which can not be done so far (without
  manual intervention, one API at the time). Automated testing of
  identity v2 and v3 API is done with default v2 policy.json file in
  Tempest, which is seriously limited and doesn't count with v3 model at
  all (domain concepts and scoping, admin role, etc.).

  Would it be possible to either go with the new
  policy.v3cloudsample.json file as default (if it's of course backward-
  compatible with v2) or use different policy file for different
  keystone API running at the same time? Without some solution, we can
  not properly test majority of v3 API functionality automatically.

  This approach could help with issues here:
  https://blueprints.launchpad.net/tempest/+spec/multi-keystone-api-version-tests
  https://bugs.launchpad.net/keystone/+bug/968696 ("admin"-ness not properly scoped)

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