Bug #41760
rgw: ldap auth: S3 auth failure should return InvalidAccessKeyId for consistency
Status:
Resolved
Priority:
Normal
Assignee:
-
Target version:
-
% Done:
0%
Source:
Tags:
Backport:
nautilus,mimic,luminous
Regression:
No
Severity:
3 - minor
Reviewed:
Description
The error reported to S3 should be the same for LDAP as for other auth mechanisms.
Related issues
History
#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
#2 Updated by Casey Bodley over 4 years ago
- Status changed from Fix Under Review to 7
#3 Updated by Casey Bodley over 4 years ago
- Status changed from 7 to Pending Backport
#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
#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
#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
#7 Updated by Nathan Cutler about 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".