-
Notifications
You must be signed in to change notification settings - Fork 80
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
401 "Unauthorised" on all requests. #3
Comments
Ran your script using the credentials I use with the gem in production and I'm able to successfully retrieve a case, but I get an error in the second part of the script:
I haven't had a chance to investigate any further yet. |
interesting, is is possible our version of faraday is different to yours in some way? |
It looks like we're running the same: faraday (0.7.5)
faraday_middleware (0.7.0) |
If you make a brand new directory and use RVM to have a clean slate with just Assistly, OAuth, and JSON, are you able to connect? |
I created a new gemset and went to install the assistly gem:
Looks like rash has been recently updated, so installed the older version:
Then installed the assistly, json and oauth gems and re-ran my test (http://pastie.org/private/r6bfn2cmg4r8i0pdetllq -- updated as I was being lazy with some requires due to the fact I was including from rails):
|
do you need any more information from me? |
Did you figure this out? I've seen this error come up when something in the request is invalid/unsupported by the Assistly/Desk API. Nothing's jumping out at me in your request, but it'd be worth checking in to. |
Hi Guys,
Every time I try and access the assitly API through the gem, it throws me out with a 401 unauthorised.
I wrote a small script to test with, to ensure OAuth itself was working. I assume there's something perhaps not working 100% when it gets through to faraday, but I can't be sure.
Test Code:
http://pastie.org/private/yhbgdqfgpgxutbmjwm2pqw
Output:
Installed gems:
The text was updated successfully, but these errors were encountered: