[GH-ISSUE #1300] Support for OpenStack Identity API v3 #696

New issue

Closed

opened 2026-03-04 01:47:59 +03:00 by kerem · 3 comments

kerem commented

2026-03-04 01:47:59 +03:00

Owner

Originally created by @ocafebabe on GitHub (May 26, 2020).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1300

Hi,

This is more a feature request than a bug: I'm currently using S3FS with an object storage that is S3 compatible (OpenStack Swift) and this works perfectly well. But my cloud provider (OVH) has warned me that support for the Identity API v2 is going to be deprecated by June 23rd and replaced completely by v3.

With v2, I didn't have to do anything special to make it work with S3FS, but I'm afraid that it'll stop working as soon as the new API is deployed...

I was wondering if there was a way to use the new API with S3FS, especially the new domain attribute that is now mandatory with the new version.

Thanks

Originally created by @ocafebabe on GitHub (May 26, 2020). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/1300 Hi, This is more a feature request than a bug: I'm currently using S3FS with an object storage that is S3 compatible (OpenStack Swift) and this works perfectly well. But my cloud provider (OVH) has warned me that support for the [Identity API v2](https://docs.openstack.org/keystone/pike/contributor/http-api.html) is going to be deprecated by June 23rd and replaced completely by [v3](https://docs.openstack.org/api-ref/identity/v3/index.html). With v2, I didn't have to do anything special to make it work with S3FS, but I'm afraid that it'll stop working as soon as the new API is deployed... I was wondering if there was a way to use the new API with S3FS, especially the new **domain** attribute that is now mandatory with the new version. Thanks

kerem closed this issue

2026-03-04 01:47:59 +03:00

kerem commented

2026-03-04 01:48:00 +03:00

Author

Owner

@gaul commented on GitHub (May 27, 2020):

Sorry I don't understand this request. Does OVH have a different authentication scheme than signature v4? If so it is not S3-compatible.

@gaul commented on GitHub (May 27, 2020): Sorry I don't understand this request. Does OVH have a different authentication scheme than signature v4? If so it is not S3-compatible.

kerem commented

2026-03-04 01:48:00 +03:00

Author

Owner

@ggtakec commented on GitHub (May 27, 2020):

I don't think the difference between Openstack Identiy v2 and v3 affects s3fs.
If currently you can access swift (using identiy v2) with s3fs, I think that you are using Access Key/Secret Access Key of Identiy (Openstack) user.
If your openstack changes to Identiy v3 and the Access Key/Secret Access Key which you are currently using to access Swift is no longer available, I think you will have problems.
However, even if the authentication API changes, I believe that it does not affect the Access Key/Secret Access Key.
(Unfortunately, I have no deep knowledge of Openstack, so please forgive me if I made a mistake)

@ggtakec commented on GitHub (May 27, 2020): I don't think the difference between Openstack Identiy v2 and v3 affects s3fs. If currently you can access swift (using identiy v2) with s3fs, I think that you are using `Access Key/Secret Access Key` of Identiy (Openstack) user. If your openstack changes to Identiy v3 and the `Access Key/Secret Access Key` which you are currently using to access Swift is no longer available, I think you will have problems. However, even if the authentication API changes, I believe that it does not affect the `Access Key/Secret Access Key`. (Unfortunately, I have no deep knowledge of Openstack, so please forgive me if I made a mistake)

kerem commented

2026-03-04 01:48:00 +03:00

Author

Owner

@ocafebabe commented on GitHub (May 27, 2020):

Sorry I don't understand this request. Does OVH have a different authentication scheme than signature v4? If so it is not S3-compatible.

No, they're S3 compatible with the v4 signature, I was talking about the identity system of OpenStack which is the one running underneath the compatibility layer...

@ocafebabe commented on GitHub (May 27, 2020): > Sorry I don't understand this request. Does OVH have a different authentication scheme than signature v4? If so it is not S3-compatible. No, they're S3 compatible with the v4 signature, I was talking about the identity system of OpenStack which is the one running underneath the compatibility layer...

kerem referenced this issue

2026-03-04 02:02:00 +03:00

[PR #1002] [MERGED] Correctly calculate MD5 hash for SSE-C keys #1754