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

swauth ignores path in cf.authentication.context in windows v4.4.1 #7526

Closed
cyberduck opened this issue Oct 29, 2013 · 5 comments
Closed

swauth ignores path in cf.authentication.context in windows v4.4.1 #7526

cyberduck opened this issue Oct 29, 2013 · 5 comments
Assignees
Labels
bug fixed openstack OpenStack Swift Protocol Implementation
Milestone

Comments

@cyberduck
Copy link
Collaborator

42245dc created the issue

the authentication path for my openstack swift server is /auth/v1.0
it worked fine in version 4.3.x after adding to the appropriate user.config
now that I've upgraded to 4.4.1 I get a 412 error, which shows the GET path as /v1.0 rather than /auth/v1.0
downgrading fixes the problem
I've verified this on 2 machines now


Attachments

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Same issue reported in #7518.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The property was renamed to openstack.authentication.context.

@cyberduck
Copy link
Collaborator Author

42245dc commented

thanks that did it!

@cyberduck
Copy link
Collaborator Author

@dkocher commented

Replying to [comment:4 Bradley Andrews]:

thanks that did it!

Fixed documentation.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

We have added a Openstack Swift (Swauth) profile that make the change of a hidden configuration setting unecessary. I recommend installing the connection profile.

@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 fixed openstack OpenStack Swift Protocol Implementation
Projects
None yet
Development

No branches or pull requests

2 participants