Project

General

Profile

Actions
Copy link

Bug #41189

closed

rgw: Put User Policy is sensitive to whitespace

Added by Abhishek Lekshmanan over 4 years ago. Updated over 4 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Tags:
Backport:
nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
29578
Crash signature (v1):
Crash signature (v2):

Description

Currently a json document like 

{
    "Version":"2012-10-17",
    "Statement": [
        {
            "Effect": "Allow",
            "Action": "s3:ListAllMyBuckets",
            "Resource": ["*"],
            "Condition": {
                "BoolIfExists": {
                    "sts:Authentication": "false" 
                }
            }
        }
    ]
}

would fail Put User Policy which is usually processed as a POST request and form is urlencoded as expected.

Related issues 1 (0 open — 1 closed)

Copied to rgw - Backport #41459: nautilus: rgw: Put User Policy is sensitive to whitespaceResolvedNathan CutlerActions
Actions
Copy link
 #1

Updated by Abhishek Lekshmanan over 4 years ago

Abhishek Lekshmanan wrote:

Currently a json document like
[...]

would fail Put User Policy which is usually processed as a POST request and form is urlencoded as expected.

eg. reproducer using aws cli

aws iam put-user-policy --user-name s3test1 --endpoint=http://localhost:8000 --policy-name foo --policy-document=file://user.json

Actions
Copy link
 #2

Updated by Casey Bodley over 4 years ago

  • Status changed from New to Fix Under Review
  • Pull request ID set to 29578
Actions
Copy link
 #3

Updated by Matt Benjamin over 4 years ago

  • Status changed from Fix Under Review to 17
Actions
Copy link
 #4

Updated by Casey Bodley over 4 years ago

  • Status changed from 17 to Pending Backport
Actions
Copy link
 #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41459: nautilus: rgw: Put User Policy is sensitive to whitespace added
Actions
Copy link
 #6

Updated by Nathan Cutler over 4 years ago

  • Status changed from Pending Backport to Resolved

While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".

Actions
Copy link

Also available in: Atom PDF