webdav is ready for use with any access key or only admin ?

[ivanfmartinez]

I have tried to use the webdav access (1.0.0-beta-3) and cannot make it work with created access keys.

It works fine with the main access key (from env RUSTFS_ACCESS_KEY), like on the readme example.

When using other access keys, the login is working, confirmed by log message.
Access do / which should list buckets give empty response, and access to other paths like /bucket-name/ returns forbidden.

I have used a allow allow policy S3:* and arn:aws:s3:::* resource.

[For8stt]

Afaik WebDAV should not be admin-only if normal access keys are expected to work with IAM/policies.

Given that auth succeeds but:

• / returns an empty bucket list
• /bucket-name/ returns 403
• same setup works with the main RUSTFS_ACCESS_KEY

this looks more like an authz/policy handling issue in the WebDAV layer, not a client-side issue.

I’d first check whether the same created access key works through S3 API / mc:

mc alias set rustfs http://localhost:9000 ACCESS_KEY SECRET_KEY
mc ls rustfs
mc ls rustfs/bucket-name

If that works via S3 but fails via WebDAV, then WebDAV is probably not applying non-admin access-key policies correctly.

Also maybe worth testing both bucket-level and object-level resources in the policy:

{
  "Effect": "Allow",
  "Action": "s3:*",
  "Resource": [
    "arn:aws:s3:::*",
    "arn:aws:s3:::*/*"
  ]
}

But imo if the main key works and a created key with full S3 permissions does not, this sounds like a WebDAV permission bug or missing support for non-root access keys.