Re: [ceph-users] radosgw cloud sync aws s3 auth failed

2019-04-08 Thread Robin H. Johnson
On Mon, Apr 08, 2019 at 06:38:59PM +0800, 黄明友 wrote:
> 
> hi,all
> 
>I had test the cloud sync module in radosgw.  ceph verion is
>13.2.5  , git commit id is
>cbff874f9007f1869bfd3821b7e33b2a6ffd4988;
Reading src/rgw/rgw_rest_client.cc
shows that it only generates v2 signatures for the sync module :-(

AWS China regions are some of the v4-only regions.

I don't know of any current work to tackle this, but there is v4
signature generation code already in the codebase, would just need to be
wired up in src/rgw/rgw_rest_client.cc.

-- 
Robin Hugh Johnson
Gentoo Linux: Dev, Infra Lead, Foundation Treasurer
E-Mail   : robb...@gentoo.org
GnuPG FP : 11ACBA4F 4778E3F6 E4EDF38E B27B944E 34884E85
GnuPG FP : 7D0B3CEB E9B85B1F 825BCECF EE05E6F6 A48F6136


signature.asc
Description: PGP signature
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com


[ceph-users] radosgw cloud sync aws s3 auth failed

2019-04-08 Thread 黄明友

hi,all

   I had test the cloud sync module in radosgw.  ceph verion is 13.2.5  , 
git commit id is  cbff874f9007f1869bfd3821b7e33b2a6ffd4988;

when sync to a aws s3 endpoint ,get http 400 error , so I use http:// protocol 
,use the tcpick tool to  dump some message like this.

PUT /wuxi01 HTTP/1.1


  
Host: s3.cn-north-1.amazonaws.com.cn
Accept: */*
Authorization: AWS AKIAUQ2G7NKZFVDQ76FZ:7ThaXKa3axR7Egf1tkwZc/YNRm4=
Date: Mon, 08 Apr 2019 10:04:37 +
Content-Length: 0
HTTP/1.1 400 Bad Request
x-amz-request-id: 65803EFC370CF11A
x-amz-id-2: 
py6N1QJw+pd91mvL0XpQhiwIVOiWIUprAX8PwAuSVOx3vrqat/Ka+xIVW3D1zC0+tJSLQyr4qC4=
x-amz-region: cn-north-1
Content-Type: application/xml
Transfer-Encoding: chunked
Date: Mon, 08 Apr 2019 10:04:37 GMT
Connection: close
Server: AmazonS3
144

InvalidRequestThe authorization mechanism you have 
provided is not supported. Please use 
AWS4-HMAC-SHA256.65803EFC370CF11Apy6N1QJw+pd91mvL0XpQhiwIVOiWIUprAX8PwAuSVOx3vrqat/Ka+xIVW3D1zC0+tJSLQyr4qC4=
0



it looks like that the client use a old auth method, not use the 
aws4-hmac-sha256. but , how can enable the aws4-hmac-sha256 auth method?___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com