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

Prompt for tenant #7836

Closed
cyberduck opened this issue Mar 4, 2014 · 6 comments
Closed

Prompt for tenant #7836

cyberduck opened this issue Mar 4, 2014 · 6 comments
Assignees
Labels
bug cloudfiles Rackspace CloudFiles fixed
Milestone

Comments

@cyberduck
Copy link
Collaborator

fa19af6 created the issue

Version 4.4 prompts for a tenant, although it doesn't allow you to enter one. Authentication then fails.

Version 4.2.1 (which doesn't prompt for a tenant) connects successfully with the same username and password.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Can you reproduce this issue with the latest snapshot build available?

@cyberduck
Copy link
Collaborator Author

fa19af6 commented

The latest nightly allows you to enter a tenant, however, AFAIK Rackspace Cloud Files don't use it. Leaving the field empty results in a timeout. 4.2.1 doesn't prompt for a tenant at all and is fine.

@cyberduck
Copy link
Collaborator Author

fa19af6 commented

I've just discovered that this can be fixed (worked around?) by using "identity.api.rackspacecloud.com" as the server. With the previous version I was using "storage.clouddrive.com", which continues to work with 4.2 but fails with newer versions.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

In 476b516.

@cyberduck
Copy link
Collaborator Author

fa19af6 commented

Hm, so Cyberduck just doesn't support the "storage.clouddrive.com" domain anymore?

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:6 matthew dapena-tretter]:

Hm, so Cyberduck just doesn't support the "storage.clouddrive.com" domain anymore?

It is not taken into account when the bookmark is configured with the protocol setting Rackspace Cloudfiles as we will always authenticate with the identity server at identity.api.rackspacecloud.com.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug cloudfiles Rackspace CloudFiles fixed
Projects
None yet
Development

No branches or pull requests

2 participants