We have just figured out what caused the authentication issue. Before doing any quota-related operations we need to manually assign the ResellerAdmin role to our user. By default, even if it's an admin user it does not have the ResellerAdmin role assigned.

Right now we have successfully executed both "swift post -m quota-bytes:5000" and "swift --os-storage-url https://<proxy-url>/v1/AUTH_<PROJECT-ID> post -m quota-bytes:5000". But after this step we can still upload files that are much larger than 5000 bytes to containers. Are there any other prerequisites that we miss? In order to let the project level quota work, what else do we need to implement?

From: Thomas Goirand <zigo@debian.org>
Sent: Wednesday, April 26, 2023 2:59 PM
To: Xu, Wei [E CPE] <weixu@iastate.edu>; openstack-discuss@lists.openstack.org <openstack-discuss@lists.openstack.org>
Cc: Babu, Sarath [E CPE] <sarath4@IASTATE.EDU>
Subject: Re: OpenStack Swift quota

On 4/26/23 21:51, Xu, Wei [E CPE] wrote:
> Hello Thomas,
>
> According to what we read from the OpenStack Swift quota documentation,
> only users with ResellerAdmin role can change the project quota
> settings. Right now for our Admin user we have already obtained the
> ResellerAdmin role (See the screenshot below), and yet we are still
> receiving the same 403 forbidden error. I believe the command itself is
> not having any errors and the Swift log did not record all these 403
> errors. I doubt could it be somewhere in the Keystone that is buggy?

Hi,

Please avoid HTML and screenshots when sending to mailing lists.

Have you checked that you have the quota middleware activated (and at
the correct position) in your swift proxy pipeline?

Cheers,

Thomas Goirand (zigo)