-
Notifications
You must be signed in to change notification settings - Fork 206
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
Working Branch Authentication #414
Comments
I'm not able to see what's going on. Can you turn on the HTTP debugging so I can see what the request looks like? In the traceback above is the line:
Just before the call to
...and then paste the output here? Be sure to obscure your actual credentials. |
Sure, I wanted to provide more debug info but wasn't sure exactly what that would be. Thanks for the explanation.
|
Sorry for the delay in responding - been swamped!! I see that your authentication request is the wrong URI:
This should have |
@EdLeafe That was it, thank you! |
@EdLeafe I can now connect, but unfortnately, with v2 I can not use the Rackspace Files CDN. For a container that has CDN enabled, Is there a way to get both the auth and CDN working with either v1 or v2 on pyrax 1.9.0? |
That should have been fixed in #423, and my tests show it working. Are you sure you have upgraded completely to 1.9.0? Or could it be using an older pyrax? What do you get if you run:
|
|
I think what happened is we were using a combination of swiftclient and pyrax for compatibility and feature requirements and that is where things get hairy because in that in one of our management commands we are always using swiftclient but in our storage class we have a conditional for swiftclient/pyrax. Now that CDN is fixed, we should be able to clean this up on our side. Hopefully this is the case and I can push a fix today. |
This reverts commit b7d503f.
This reverts commit 31973aa.
This reverts commit b7d503f.
This reverts commit 31973aa.
I'm testing out django-cumulus with the lastest pyrax commit on the working branch, which resolves other bugfixes I'm looking forward to landing, however something has changed because authentication is no longer working (the latest release authenticates just fine). Do you have any suggestions as to what it could be? Are there backwards incompatible changes coming that I should fix upstream in the django cumulus library?
I hit this traceback with any
manage.py
command:The text was updated successfully, but these errors were encountered: