Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Oracle Object Storage pre-signed url error #11555

Closed
cyberduck opened this issue Jan 24, 2021 · 8 comments
Closed

Oracle Object Storage pre-signed url error #11555

cyberduck opened this issue Jan 24, 2021 · 8 comments
Assignees
@dkocher
Labels
bug fixed s3 AWS S3 Protocol Implementation
Milestone
7.9.1

Comments

@cyberduck
Copy link
Collaborator

05e58ef created the issue

The pre-signed url cannot be accessed via right-click-menu.
The respond is

This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Message>Either the bucket named 'test' does not exist in the namespace '*BucketNameOfFile*' or you are not authorized to access it. Your namespace is not *BucketNameOfFile*.</Message>
<Code>NoSuchBucket</Code>
</Error>

-BucketNameOfFile* refers the bucket's name where the file located.
It seems the generated url consisted my bucket name instead of namespace.
This bug shows on both Windows 10 and Macos 11 with version 7.8.2(34160/34161)

Please fix that, thanks.

Attachments
@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you please try if still see this issue with the current snapshot build
by updating from within Cyberduck in ''Preferences → Update →
Automatically check for updates in → Snapshot Builds''. Please install the latest profile from Oracle Cloud Infrastructure which has a new setting to use path-style requests. See also #10956.

@cyberduck
Copy link
Collaborator Author

05e58ef commented

Thanks for your kindly reply!
I've tried to update to the latest version of Cyberduck ( 7.8.2 34164 Windows ) and re-download and import profile above, but the error still exists with the unsecure connection prompt.


This XML file does not appear to have any style information associated with it. The document tree is shown below.
<Error>
<Message>Either the bucket named 'test' does not exist in the namespace 'img' or you are not authorized to access it. Your namespace is not img.</Message>
<Code>NoSuchBucket</Code>
</Error>

The Screen shot will be attached to the thread.

Just for your info, I've tried S3 Browser, and it seems the url generated in S3 Browser did not contains the bucket name and start with namespace.
Thanks!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you provide a temporary account for testing and reproducing the issue?

@cyberduck
Copy link
Collaborator Author

05e58ef commented

The credential and more screenshots has been sent to your mail(dkocher#iterate.ch), Here is some of the reproducing steps:
1.log in with the credential in your email.
2. choose Bucket named 'testprivatebucket' ,select the test file, and use right click menu to generate a Pre-signed url.
3. open the link in a brower,then dismiss the cert error.
4.The error message will be shown.
Screenshots will be attached to this reply.
You may reply my mail for more info.

@cyberduck
Copy link
Collaborator Author

05e58ef commented

BTW, certification error is just because the url contains the bucket's name, it seems the correct url is

https://<namespace>.compat.objectstorage.ap-tokyo-1.oraclecloud.com/<bucketname>/<filename>.txt?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=<Access Key>/20210127/ap-tokyo-1/s3/aws4_request&X-Amz-Date=20210127T043352Z&X-Amz-Expires=3600&X-Amz-SignedHeaders=host&X-Amz-Signature=<signature>

Since I cannot do any programming, so please test this url by generate corresponding signature.

@cyberduck
Copy link
Collaborator Author

05e58ef commented

Replying to [comment:4 dkocher]:

Can you provide a temporary account for testing and reproducing the issue?

Sorry for asking, but is there anything I can help to fix the bug?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:7 hanaw]:

Replying to [comment:4 dkocher]:

Can you provide a temporary account for testing and reproducing the issue?

Sorry for asking, but is there anything I can help to fix the bug?
I can reproduce the issue with the provided account.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In d2b909c.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 27, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@dkocher dkocher

Labels
bug fixed s3 AWS S3 Protocol Implementation
Projects
None yet
Milestone
7.9.1
Development

No branches or pull requests
2 participants
@dkocher @cyberduck