Zaqar shouldn't use policy.json, when auth method is noauth

Bug #1540658 reported by Eva Balycheva on 2016-02-01
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Eva Balycheva

Bug Description

Currently, when I switch Zaqar to use noauth, the policy, which is defined in policy.json, is still enforced for Zaqar API v2.

Zaqar returns 403 response code for all admin actions defined in policy.json.

Even if I provide keystone token, Zaqar wouldn't authorize me and allow me to do admin actions.

Eva Balycheva (ubershy) on 2016-02-01
Changed in zaqar:
assignee: nobody → Eva Balycheva (ubershy)
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers