Project

General

Profile

Actions
Copy link

Bug #41760

closed

rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistency

Added by Matt Benjamin over 4 years ago. Updated over 3 years ago.

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

0%

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

Description

The error reported to S3 should be the same for LDAP as for other auth mechanisms.

Related issues 3 (0 open — 3 closed)

Copied to rgw - Backport #41969: luminous: rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistencyRejectedActions
Copied to rgw - Backport #41970: nautilus: rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistencyResolvedPrashant DActions
Copied to rgw - Backport #41971: mimic: rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistencyResolvedPrashant DActions
Actions
Copy link
 #1

Updated by Matt Benjamin over 4 years ago

  • Status changed from In Progress to Fix Under Review
  • Backport set to nautilus,mimic,luminous
  • Pull request ID set to 30332
Actions
Copy link
 #2

Updated by Casey Bodley over 4 years ago

  • Status changed from Fix Under Review to 7
Actions
Copy link
 #3

Updated by Casey Bodley over 4 years ago

  • Status changed from 7 to Pending Backport
Actions
Copy link
 #4

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41969: luminous: rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistency added
Actions
Copy link
 #5

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41970: nautilus: rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistency added
Actions
Copy link
 #6

Updated by Nathan Cutler over 4 years ago

  • Copied to Backport #41971: mimic: rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistency added
Actions
Copy link
 #7

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