Project

General

Profile

Actions
Copy link

Bug #42218

closed

rgw: SignatureDoesNotMatch when s3 client use ipv6 address

Added by joke lee over 4 years ago. Updated about 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:
30778
Crash signature (v1):
Crash signature (v2):

Description

here is my s3 java sdk test ipv6

AWSCredentials credentials = new BasicAWSCredentials("yly", "yly");
        ClientConfiguration s3_opts = new ClientConfiguration();
        s3_opts.setSignerOverride("S3SignerType");
        AmazonS3 s3_client = new AmazonS3Client(credentials, s3_opts);
        s3_client.setEndpoint("http://[2409:8050:3000:5000:1400::238]");
        s3_client.setS3ClientOptions(new S3ClientOptions().withPathStyleAccess(true));
        s3_client.listObjects("test1");
and it is 403 SignatureDoesNotMatch error

the rgw log below

2019-10-08T15:00:45.853+0800 7f5571da4700 15 req 1 0.007999973s s3:get_obj string_to_sign=GET

application/octet-stream
Tue, 08 Oct 2019 07:00:45 GMT
/[2409/test1/
2019-10-08T15:00:45.853+0800 7f5571da4700 15 req 1 0.007999973s s3:get_obj server signature=uWtjhLmR4ADsAdmrRWgTnJrRObI=
2019-10-08T15:00:45.853+0800 7f5571da4700 15 req 1 0.007999973s s3:get_obj client signature=3Ad+klS9c4Irf+A/D/4YGgUgE4M=
2019-10-08T15:00:45.853+0800 7f5571da4700 15 req 1 0.007999973s s3:get_obj compare=-66
2019-10-08T15:00:45.853+0800 7f5571da4700 20 req 1 0.007999973s s3:get_obj rgw::auth::s3::LocalEngine denied with reason=-2027
2019-10-08T15:00:45.853+0800 7f5571da4700 20 req 1 0.007999973s s3:get_obj rgw::auth::s3::AWSAuthStrategy denied with reason=-2027
2019-10-08T15:00:45.853+0800 7f5571da4700 20 req 1 0.007999973s s3:get_obj rgw::auth::StrategyRegistry::s3_main_strategy_t: trying rgw::auth::s3::AWSAuthStrategy
2019-10-08T15:00:45.853+0800 7f5571da4700 20 req 1 0.007999973s s3:get_obj rgw::auth::s3::AWSAuthStrategy: trying rgw::auth::s3::LocalEngine
2019-10-08T15:00:45.853+0800 7f5571da4700 10 get_canon_resource(): dest=/[2409/test1/
2019-10-08T15:00:45.853+0800 7f5571da4700 10 req 1 0.007999973s string_to_sign:
GET

application/octet-stream
Tue, 08 Oct 2019 07:00:45 GMT
/[2409/test1/ <== wrong here
2019-10-08T15:00:45.853+0800 7f5571da4700 15 req 1 0.007999973s s3:get_obj string_to_sign=GET

application/octet-stream
Tue, 08 Oct 2019 07:00:45 GMT
/[2409/test1/

Related issues 1 (0 open — 1 closed)

Copied to rgw - Backport #43855: nautilus: rgw: SignatureDoesNotMatch when s3 client use ipv6 addressResolvedNathan CutlerActions
Actions
Copy link
 #2

Updated by Nathan Cutler over 4 years ago

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

Updated by Casey Bodley over 4 years ago

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

Updated by Matt Benjamin over 4 years ago

  • Backport set to nautilus
Actions
Copy link
 #5

Updated by Patrick Donnelly over 4 years ago

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

Updated by Casey Bodley about 4 years ago

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

Updated by Nathan Cutler about 4 years ago

  • Copied to Backport #43855: nautilus: rgw: SignatureDoesNotMatch when s3 client use ipv6 address added
Actions
Copy link
 #8

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
Copy link

Also available in: Atom PDF