github-asana icon indicating copy to clipboard operation
github-asana copied to clipboard

Last Delivery was not successful. Not Authorized

Open mattuuh7 opened this issue 10 years ago • 10 comments

got the below message: Last Delivery was not successful. Not Authorized Any idea what the problem is? I used the token created in Asana and use it in the github repo settings

mattuuh7 avatar Sep 21 '15 18:09 mattuuh7

Same problem here. I was wondering if it had something to do with the different email addresses I used between Asana and GitHub.

npanchaud avatar Sep 22 '15 13:09 npanchaud

Same problem. By the way I use different email ids for both services.

AlokBansal8 avatar Oct 05 '15 16:10 AlokBansal8

+1 And yes I too use different emails for both.

abhimskywalker avatar Oct 10 '15 07:10 abhimskywalker

+1 and different emails

VivaBem avatar Oct 14 '15 17:10 VivaBem

Ok, so I just noticed the syntax of key being added here:

heroku config:add ASANA_USERS='[{"username":"GitHubUsername1", "key":"XXXXXXXX.XXXXXXXXXXXXXXXXXX"}, {"username":"GitHubUsername2", "key":"XXXXXXXX.XXXXXXXXXXXXXXXXXX"}]'

I was trying to use the Personal Access Tokens from the Asana's My Profile Settings > Apps section. But this seems like format of the API key.

Asana notes on this API key:

*API Key*
Asana has an API which allows integration with external applications. Applications that do not use Asana Connect use this key for authentication. 

@mattuuh7 @npanchaud @AlokBansal8 @olharsaude Can you guys also once confirm if using this API key works out fine for you? And if you were originally using this Personal Access Tokens as well like me for this?

abhimskywalker avatar Oct 14 '15 17:10 abhimskywalker

API keys are actually deprecated and on the way out. If some of you would like a deeper integration, we built an Asana-GitHub sync service at http://unito.io . Still in private beta, but we invite users on the same or next day usually. We're a couple of weeks from public beta.

marcboscher avatar Oct 14 '15 18:10 marcboscher

@abhimskywalker, using the "API key" works fine!

Thank you for the help!

VivaBem avatar Oct 15 '15 09:10 VivaBem

@marcboscher I can still use personal access token and can see that the test payload succeeded. But still not able to get proper sync up on the message. Might this be internal firewall setup you have seen before?

mattuuh7 avatar Oct 19 '15 17:10 mattuuh7

sorry @mattuuh7 , can't really help you with this project (I actually build the http://unito.io alternative). I don't think personal access tokens behave the same way as API keys.

Here's the link to the Asana article foretelling the end-of-life of API keys: https://asana.com/developers/feed/api-key-deprecation

marcboscher avatar Oct 20 '15 00:10 marcboscher

Thanks. Will take a look. I am going to close the ticket.

Matt Chen

On Oct 19, 2015, at 17:22, Marc Boscher [email protected] wrote:

sorry @mattuuh7 , can't really help you with this project (I actually build the http://unito.io alternative). I don't think personal access tokens behave the same way as API keys.

Here's the link to the Asana article foretelling the end-of-life of API keys: https://asana.com/developers/feed/api-key-deprecation

— Reply to this email directly or view it on GitHub.

mattuuh7 avatar Oct 20 '15 00:10 mattuuh7