Project

General

Profile

Actions

Bug #42911

closed

Changing bucket versioning status for an MFA enabled bucket works without asking for an MFA code

Added by Pritha Srivastava over 4 years ago. Updated about 4 years ago.

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

0%

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

Description

As per https://docs.aws.amazon.com/AmazonS3/latest/dev/Versioning.html#MultiFactorAuthenticationDelete, changing the versioning status for an MFA enabled bucket should require the MFA code to be passed in.


Related issues 2 (0 open2 closed)

Copied to rgw - Backport #43202: mimic: Changing bucket versioning status for an MFA enabled bucket works without asking for an MFA codeResolvedNathan CutlerActions
Copied to rgw - Backport #43203: nautilus: Changing bucket versioning status for an MFA enabled bucket works without asking for an MFA codeResolvedNathan CutlerActions
Actions #1

Updated by Pritha Srivastava over 4 years ago

  • Status changed from New to In Progress
Actions #2

Updated by Casey Bodley over 4 years ago

  • Status changed from In Progress to 7
  • Pull request ID set to 31767
Actions #3

Updated by Patrick Donnelly over 4 years ago

  • Status changed from 7 to Fix Under Review
Actions #4

Updated by Casey Bodley over 4 years ago

  • Status changed from Fix Under Review to Pending Backport
  • Backport set to mimic nautilus
Actions #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43202: mimic: Changing bucket versioning status for an MFA enabled bucket works without asking for an MFA code added
Actions #6

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #43203: nautilus: Changing bucket versioning status for an MFA enabled bucket works without asking for an MFA code added
Actions #7

Updated by Nathan Cutler about 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

Also available in: Atom PDF