-
Notifications
You must be signed in to change notification settings - Fork 301
Can't update Stashboard using API #9
Comments
Is there any news regarding this issue ? I have the same situation. |
I have a similar problem, which I posted to Google Groups, only I get a 405 instead of 403. This seems to be common problem. Please, folks, you've written such a neat app, can you just help us out so we can use your awesomeness? |
@pburkholder The 405 is a different error, but may suffer from the same underlying problem. There are two APIs that stashboard provides. A read-only public API and a read/write API for account owners. The reason there are two APIs is that App Engine only let's you set authentication levels in the app.yaml. To be absolutely sure that you access the API over SSL and are authenticated, you need to use the For further reference, please take a look at the REST API docs. https://stashboard.readthedocs.org/en/latest/restapi.html |
I am seeing this with stashboard on google apps. Use the OAuth credentials given to us, then access the /admin/ endpoints, and we're rejected because the OAuth credentials are considered by Google to be bogus. |
this big affects me too. I get: {u'message': u'Authorization Failure', u'code': 403, u'error': True} I also tried github ruby project stashboard-notifier and get same error. has anyone got a working api for stashboard? |
Check your system time, I was bitten by this today - in one interpreter it was working fine, but in another it was failing. After tracing and observing that there is a time bound nonce in the OAuth response (and reading that tokens have a 10 minute TTL) I checked my system time... it was out by > 10 minutes; setting up NTP and updating the time fixed the issue. |
In our case the OAuth credentials had changed. Go to https://.appspot.com/admin/credentials to verify that they're ok. |
I can login to appspot.com and manually edit Stashboard, but the API fails with 403 errors using both the Python and Ruby example clients.
I'm using the consumer key and secret I got when registering the app with Google. This is from the logs when I used both example clients:
See details
See details
The text was updated successfully, but these errors were encountered: